AsyncClient GetHeader Method Aerospike
Overload List

  NameDescription
Public methodGetHeader(BatchPolicy,  Key )
Read multiple record header data for specified keys in one batch call. The returned records are in positional order with the original key array order. If a key is not found, the positional record will be null. The policy can be used to specify timeouts and maximum concurrent threads.
(Inherited from AerospikeClient.)
Public methodGetHeader(Policy, Key)
Read record generation and expiration only for specified key. Bins are not read. If found, return record instance. If not found, return null. The policy can be used to specify timeouts.
(Inherited from AerospikeClient.)
Public methodGetHeader(Policy,  Key )Obsolete.
Read multiple record header data for specified keys in one batch call. The returned records are in positional order with the original key array order. If a key is not found, the positional record will be null. The policy can be used to specify timeouts.
(Inherited from AerospikeClient.)
Public methodGetHeader(Policy, RecordArrayListener,  Key )
Asynchronously read multiple record header data for specified keys in one batch call. This method schedules the get command with a channel selector and returns. Another thread will process the command and send the results to the listener in a single call.

If a key is not found, the record will be null. The policy can be used to specify timeouts.

Public methodGetHeader(Policy, RecordListener, Key)
Asynchronously read record generation and expiration only for specified key. Bins are not read. This method schedules the get command with a channel selector and returns. Another thread will process the command and send the results to the listener.

The policy can be used to specify timeouts.

Public methodGetHeader(Policy, RecordSequenceListener,  Key )
Asynchronously read multiple record header data for specified keys in one batch call. This method schedules the get command with a channel selector and returns. Another thread will process the command and send the results to the listener in multiple unordered calls.

If a key is not found, the record will be null. The policy can be used to specify timeouts.

Back to Top
See Also