BatchPolicy useBatchDirect FieldAerospike
Use old batch direct protocol where batch reads are handled by direct low-level batch server database routines. The batch direct protocol can be faster when there is a single namespace, but there is one important drawback. The batch direct protocol will not proxy to a different server node when the mapped node has migrated a record to another node (resulting in not found record).

This can happen after a node has been added/removed from the cluster and there is a lag between records being migrated and client partition map update (once per second).

The new batch index protocol will perform this record proxy when necessary. Default: false (use new batch index protocol if server supports it)

Namespace: Aerospike.Client
Assembly: AerospikeClient (in AerospikeClient.dll) Version: 3.2.0.0 (3.2.1)
Syntax

See Also