DMLOptions
Related Doc:
package cassandra
Enables tracing for this DML statement *
Whether this statement is idempotent, i.e.
Whether this statement is idempotent, i.e. whether it can be applied multiple times without changing the result beyond the initial application.
Overrides default behaviour, where statement is idempotnet when - it updates counter - it prepends / appends to the list - uses function call
Sets the consistency level for the DML statement.
Sets the default timestamp for this query (in microseconds since the epoch).
Sets the default timestamp for this query (in microseconds since the epoch).
This feature is only available when version V3 or
higher of the native protocol is in use. With earlier versions, calling this
method has no effect.
The actual timestamp that will be used for this query is, in order of preference:
the timestamp specified directly in the CQL query string (using the
USING TIMESTAMP syntax)
the timestamp specified through this method, if different from
Long#MIN_VALUE;
the timestamp returned by the TimestampGenerator currently in use,
if different from Long#MIN_VALUE.
If none of these apply, no timestamp will be sent with the query and Cassandra will generate a server-side one (similar to the pre-V3 behavior).
Sets the retry policy to use for this query.
Sets the retry policy to use for this query.
The default retry policy, if this method is not called, is the one returned by
com.datastax.driver.core.policies.Policies#getRetryPolicy in the
cluster configuration. This method is thus only useful in case you want
to punctually override the default policy for this request.
Sets the serial consistency level for the query.
Sets the serial consistency level for the query.
The serial consistency level is only used by conditional updates (INSERT, UPDATE
or DELETE statements with an IF condition).
For those, the serial consistency level defines
the consistency level of the serial phase (or "paxos" phase) while the
normal consistency level defines the consistency for the "learn" phase, i.e. what
type of reads will be guaranteed to see the update right away. For instance, if
a conditional write has a regular consistency of QUORUM (and is successful), then a
QUORUM read is guaranteed to see that write. But if the regular consistency of that
write is ANY, then only a read with a consistency of SERIAL is guaranteed to see it
(even a read with consistency ALL is not guaranteed to be enough).
The serial consistency can only be one of ConsistencyLevel.SERIAL or
ConsistencyLevel.LOCAL_SERIAL. While ConsistencyLevel.SERIAL guarantees full
linearizability (with other SERIAL updates), ConsistencyLevel.LOCAL_SERIAL only
guarantees it in the local data center.
The serial consistency level is ignored for any query that is not a conditional update (serial reads should use the regular consistency level for instance).