QueryPolicy MembersAerospike

The QueryPolicy type exposes the following members.
Constructors

  NameDescription
Public methodQueryPolicy
Default constructor.
Back to Top
Fields

  NameDescription
Public fieldconsistencyLevel
How replicas should be consulted in a read operation to provide the desired consistency guarantee.

Default: CONSISTENCY_ONE

(Inherited from Policy.)
Public fieldmaxConcurrentNodes
Maximum number of concurrent requests to server nodes at any point in time. If there are 16 nodes in the cluster and maxConcurrentNodes is 8, then queries will be made to 8 nodes in parallel. When a query completes, a new query will be issued until all 16 nodes have been queried. Default (0) is to issue requests to all server nodes in parallel.
Public fieldmaxRetries
Maximum number of retries before aborting the current transaction. A retry may be attempted when there is a network error. If maxRetries is exceeded, the abort will occur even if the timeout has not yet been exceeded.

Default: 1

(Inherited from Policy.)
Public fieldpriority
Priority of request relative to other transactions. Currently, only used for scans.
(Inherited from Policy.)
Public fieldrecordQueueSize
Number of records to place in queue before blocking. Records received from multiple server nodes will be placed in a queue. A separate thread consumes these records in parallel. If the queue is full, the producer threads will block until records are consumed.
Public fieldreplica
Send read commands to the node containing the key's partition replica type. Write commands are not affected by this setting, because all writes are directed to the node containing the key's master partition.

Default: MASTER

(Inherited from Policy.)
Public fieldretryOnTimeout
Should the client retry a command if the timeout is reached.

If false, throw timeout exception when the timeout has been reached. Note that retries can still occur if a command fails on a network error before the timeout has been reached.

If true, retry command with same timeout when the timeout has been reached. The maximum number of retries is defined by maxRetries.

Default: false
(Inherited from Policy.)
Public fieldsendKey
Send user defined key in addition to hash digest on both reads and writes.

Default: false (do not send the user defined key)

(Inherited from Policy.)
Public fieldsleepBetweenRetries
Milliseconds to sleep between retries. Do not sleep at all if zero. Used by synchronous commands only.

Default: 500ms

(Inherited from Policy.)
Public fieldtimeout
Total transaction timeout in milliseconds for both client and server. The timeout is tracked on the client and also sent to the server along with the transaction in the wire protocol. The client will most likely timeout first, but the server has the capability to timeout the transaction as well.

The timeout is also used as a socket timeout. Default: 0 (no timeout).

(Inherited from Policy.)
Back to Top
See Also