Initializes a new ApplyPolicy from the provided policy values.
Optionalprops: ApplyPolicyOptionsApplyPolicy values
OptionalcommitSpecifies the number of replicas required to be committed successfully when writing before returning command succeeded.
policy.commitLevel for supported policy values.
OptionalcompressUse 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.
@default: false
OptionaldurableSpecifies whether a http://www.aerospike.com/docs/guide/durable_deletes.html|tombstone should be written in place of a record that gets deleted as a result of this command.
OptionalfilterOptional expression filter. If filter exp exists and evaluates to false, the command 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:
OptionalkeySpecifies the behavior for the key.
policy.key for supported policy values.
OptionalmaxMaximum number of retries before aborting the current command. The initial attempt is not counted as a retry.
If maxRetries is exceeded, the command will return
error ERR_TIMEOUT.
WARNING: Database writes that are not idempotent (such as "add")
should not be retried because the write command may be performed
multiple times if the client timed out previous command attempts.
It is important to use a distinct write policy for non-idempotent
writes which sets maxRetries to zero.
@default: 2 (initial attempt + 2 retries = 3 attempts)
OptionalsocketSocket 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 command 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.
OptionaltotalTotal command timeout in milliseconds.
The totalTimeout is tracked on the client and sent to the
server along with the command in the wire protocol. The client will
most likely timeout first, but the server also has the capability to
timeout the command
If totalTimeout is not zero and totalTimeout
is reached before the command completes, the command will return
error ERR_TIMEOUT.
If totalTimeout is zero, there will be no total time limit.
OptionalttlThe time-to-live (expiration) of the record in seconds.
OptionaltxnTransaction identifier. See Transaction for more information.
Initializes a new ApplyPolicy from the provided policy values.