public final class BatchPolicy extends Policy
Modifier and Type | Field and Description |
---|---|
boolean |
allowInline
Allow batch to be processed immediately in the server's receiving thread when the server
deems it to be appropriate.
|
int |
maxConcurrentThreads
Maximum number of concurrent synchronous batch request threads to server nodes at any point in time.
|
boolean |
sendSetName
Send set name field to server for every key in the batch for batch index protocol.
|
boolean |
useBatchDirect
Use old batch direct protocol where batch reads are handled by direct low-level batch server
database routines.
|
consistencyLevel, linearizeRead, maxRetries, priority, replica, sendKey, sleepBetweenRetries, socketTimeout, timeoutDelay, totalTimeout
Constructor and Description |
---|
BatchPolicy()
Default constructor.
|
BatchPolicy(BatchPolicy other)
Copy batch policy from another batch policy.
|
BatchPolicy(Policy other)
Copy batch policy from another policy.
|
public int maxConcurrentThreads
Values:
public boolean useBatchDirect
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)
public boolean allowInline
For batch exists or batch reads of smaller sized records (<= 1K per record), inline processing will be significantly faster on "in memory" namespaces. The server disables inline processing on disk based namespaces regardless of this policy field.
Inline processing can introduce the possibility of unfairness because the server can process the entire batch before moving onto the next command. Default: true
public boolean sendSetName
public BatchPolicy(BatchPolicy other)
public BatchPolicy(Policy other)
public BatchPolicy()
Copyright ? 2012–2018 Aerospike, Inc. All rights reserved.