Class BatchWritePolicy
-
Field Summary
FieldsModifier and TypeFieldDescriptionDesired consistency guarantee when committing a command on the server.booleanIf the command results in a record deletion, leave a tombstone for the record.intRecord expiration.Optional expression filter.intExpected generation.Qualify how to handle record writes based on record generation.Qualify how to handle writes where the record already exists.booleanSend user defined key in addition to hash digest. -
Constructor Summary
ConstructorsConstructorDescriptionDefault constructor.BatchWritePolicy(BatchWritePolicy other) Copy constructor. -
Method Summary
Modifier and TypeMethodDescriptionvoidsetCommitLevel(CommitLevel commitLevel) voidsetDurableDelete(boolean durableDelete) voidsetExpiration(int expiration) voidsetFilterExp(Expression filterExp) voidsetGeneration(int generation) voidsetGenerationPolicy(GenerationPolicy generationPolicy) voidsetRecordExistsAction(RecordExistsAction recordExistsAction) voidsetSendKey(boolean sendKey)
-
Field Details
-
filterExp
Optional expression filter. If filterExp exists and evaluates to false, the specific batch key request is not performed andBatchRecord.resultCodeis set toResultCode.FILTERED_OUT.If exists, this filter overrides the batch parent filter
Policy.filterExpfor the specific key in batch commands that allow a different policy per key. Otherwise, this filter is ignored.Default: null
-
recordExistsAction
Qualify how to handle writes where the record already exists.Default: RecordExistsAction.UPDATE
-
commitLevel
Desired consistency guarantee when committing a command on the server. The default (COMMIT_ALL) indicates that the server should wait for master and all replica commits to be successful before returning success to the client.Default: CommitLevel.COMMIT_ALL
-
generationPolicy
Qualify how to handle record writes based on record generation. The default (NONE) indicates that the generation is not used to restrict writes.The server does not support this field for UDF execute() calls. The read-modify-write usage model can still be enforced inside the UDF code itself.
Default: GenerationPolicy.NONE
-
generation
public int generationExpected generation. Generation is the number of times a record has been modified (including creation) on the server. If a write operation is creating a record, the expected generation would be0. This field is only relevant when generationPolicy is not NONE.The server does not support this field for UDF execute() calls. The read-modify-write usage model can still be enforced inside the UDF code itself.
Default: 0
-
expiration
public int expirationRecord expiration. Also known as ttl (time to live). Seconds record will live before being removed by the server.Expiration values:
- -2: Do not change ttl when record is updated.
- -1: Never expire.
- 0: Default to namespace configuration variable "default-ttl" on the server.
- > 0: Actual ttl in seconds.
Default: 0
-
durableDelete
public boolean durableDeleteIf the command results in a record deletion, leave a tombstone for the record. This prevents deleted records from reappearing after node failures. Valid for Aerospike Server Enterprise Edition only.Default: false (do not tombstone deleted records).
-
sendKey
public boolean sendKeySend user defined key in addition to hash digest. If true, the key will be stored with the record on the server.Default: false (do not send the user defined key)
-
-
Constructor Details
-
BatchWritePolicy
Copy constructor. -
BatchWritePolicy
public BatchWritePolicy()Default constructor.
-
-
Method Details
-
setFilterExp
-
setRecordExistsAction
-
setCommitLevel
-
setGenerationPolicy
-
setGeneration
public void setGeneration(int generation) -
setExpiration
public void setExpiration(int expiration) -
setDurableDelete
public void setDurableDelete(boolean durableDelete) -
setSendKey
public void setSendKey(boolean sendKey)
-