Class: BatchPolicy

BatchPolicy

A policy affecting the behavior of batch operations.


new BatchPolicy( [props])

Initializes a new BatchPolicy from the provided policy values.

Parameters:
Name Type Argument Description
props Object <optional>

Policy values

Since:
  • v3.0.0
Source:

Extends

Members


allowInline :boolean

Allow batch to be processed immediately in the server's receiving thread when the server deems it to be appropriate. If false, the batch will always be processed in separate transaction threads.

Type:
  • boolean
Default Value:
  • true
Source:

allowInlineSSD :boolean

Allow batch to be processed immediately in the server's receiving thread for SSD namespaces. If false, the batch will always be processed in separate service threads. Server versions < 6.0 ignore this field.

Inline processing can introduce the possibility of unfairness because the server can process the entire batch before moving onto the next command.

Type:
  • boolean
Default Value:
  • false
Source:

compress :boolean

Use zlib compression on write or batch read commands when the command buffer size is greater than 128 bytes. In addition, tell the server to compress it's response on read commands. The server response compression threshold is also 128 bytes.

This option will increase cpu and memory usage (for extra compressed buffers), but decrease the size of data sent over the network.

Requires Enterprise Server version >= 4.8.

Type:
  • boolean
Since:
  • v3.14.0
Inherited From:
Overrides:
Source:

concurrent :boolean

Determine if batch commands to each server are run in parallel threads.

Values: false: Issue batch commands sequentially. This mode has a performance advantage for small to medium sized batch sizes because commands can be issued in the main transaction thread. This is the default. true: Issue batch commands in parallel threads. This mode has a performance advantage for large batch sizes because each node can process the command immediately. The downside is extra threads will need to be created (or taken from a thread pool).

Type:
  • boolean
Default Value:
  • false
Source:

deserialize :boolean

Should CDT data types (Lists / Maps) be deserialized to JS data types (Arrays / Objects) or returned as raw bytes (Buffer).

Type:
  • boolean
Since:
  • v3.7.0
Default Value:
  • true
Source:

filterExpression

Optional expression filter. If filter exp exists and evaluates to false, the transaction is ignored. This can be used to eliminate a client/server roundtrip in some cases.

expression filters can only be applied to the following commands:

Inherited From:
Overrides:
Source:

maxRetries :number

Maximum number of retries before aborting the current transaction. The initial attempt is not counted as a retry.

If maxRetries is exceeded, the transaction will return error ERR_TIMEOUT.

WARNING: Database writes that are not idempotent (such as "add") should not be retried because the write operation may be performed multiple times if the client timed out previous transaction attempts. It is important to use a distinct write policy for non-idempotent writes which sets maxRetries to zero.

Type:
  • number
Inherited From:
Overrides:
Source:

readModeAP :number

Read policy for AP (availability) namespaces.

Type:
  • number
Default Value:
  • Aerospike.policy.readModeAP.ONE
Source:
See:

readModeSC :number

Read policy for SC (strong consistency) namespaces.

Type:
  • number
Default Value:
  • Aerospike.policy.readModeSC.SESSION
Source:
See:

replica :number

Algorithm used to determine target node.

Type:
  • number
Default Value:
  • Aerospike.policy.replica.MASTER
Source:
See:

respondAllKeys :boolean

Should all batch keys be attempted regardless of errors. This field is used on both the client and server. The client handles node specific errors and the server handles key specific errors.

If true, every batch key is attempted regardless of previous key specific errors. Node specific errors such as timeouts stop keys to that node, but keys directed at other nodes will continue to be processed.

If false, the server will stop the batch to its node on most key specific errors. The exceptions are AEROSPIKE_ERR_RECORD_NOT_FOUND and AEROSPIKE_FILTERED_OUT which never stop the batch. The client will stop the entire batch on node specific errors for sync commands that are run in sequence (concurrent == false). The client will not stop the entire batch for async commands or sync commands run in parallel.

Server versions < 6.0 do not support this field and treat this value as false for key specific errors.

Type:
  • boolean
Default Value:
  • true
Source:

sendSetName :boolean

Send set name field to server for every key in the batch. This is only necessary when authentication is enabled and security roles are defined on a per-set basis.

Type:
  • boolean
Default Value:
  • false
Source:

socketTimeout :number

Socket idle timeout in milliseconds when processing a database command.

If socketTimeout is not zero and the socket has been idle for at least socketTimeout, both maxRetries and totalTimeout are checked. If maxRetries and totalTimeout are not exceeded, the transaction is retried.

If both socketTimeout and totalTimeout are non-zero and socketTimeout > totalTimeout, then socketTimeout will be set to totalTimeout. If socketTimeout is zero, there will be no socket idle limit.

Type:
  • number
Inherited From:
Overrides:
Default Value:
  • 0 (no socket idle time limit).
Source:

totalTimeout :number

Total transaction timeout in milliseconds.

The totalTimeout is tracked on the client and sent to the server along with the transaction in the wire protocol. The client will most likely timeout first, but the server also has the capability to timeout the transaction.

If totalTimeout is not zero and totalTimeout is reached before the transaction completes, the transaction will return error ERR_TIMEOUT. If totalTimeout is zero, there will be no total time limit.

Type:
  • number
Inherited From:
Overrides:
Default Value:
  • 1000
Source: