public abstract class Statement extends Object
This represents either a RegularStatement
, a BoundStatement
or a
BatchStatement
along with the querying options (consistency level,
whether to trace the query, ...).
Modifier and Type | Field and Description |
---|---|
protected Boolean |
idempotent |
Modifier and Type | Method and Description |
---|---|
Statement |
disableTracing()
Disables tracing for this query.
|
Statement |
enableTracing()
Enables tracing for this query.
|
ConsistencyLevel |
getConsistencyLevel()
The consistency level for this query.
|
int |
getFetchSize()
The fetch size for this query.
|
abstract String |
getKeyspace()
Returns the keyspace this query operates on.
|
RetryPolicy |
getRetryPolicy()
Returns the retry policy sets for this query, if any.
|
abstract ByteBuffer |
getRoutingKey()
Returns the routing key (in binary raw form) to use for token aware
routing of this query.
|
ConsistencyLevel |
getSerialConsistencyLevel()
The serial consistency level for this query.
|
Boolean |
isIdempotent()
Whether this statement is idempotent, i.e.
|
boolean |
isTracing()
Returns whether tracing is enabled for this query or not.
|
Statement |
setConsistencyLevel(ConsistencyLevel consistency)
Sets the consistency level for the query.
|
Statement |
setFetchSize(int fetchSize)
Sets the query fetch size.
|
Statement |
setIdempotent(boolean idempotent)
Sets whether this statement is idempotent.
|
Statement |
setPagingState(PagingState pagingState)
Sets the paging state.
|
Statement |
setPagingStateUnsafe(byte[] pagingState)
Sets the paging state.
|
Statement |
setRetryPolicy(RetryPolicy policy)
Sets the retry policy to use for this query.
|
Statement |
setSerialConsistencyLevel(ConsistencyLevel serialConsistency)
Sets the serial consistency level for the query.
|
protected volatile Boolean idempotent
public Statement setConsistencyLevel(ConsistencyLevel consistency)
consistency
- the consistency level to set.Statement
object.public ConsistencyLevel getConsistencyLevel()
null
if no
consistency level has been specified (through setConsistencyLevel
).
In the latter case, the default consistency level will be used.public Statement setSerialConsistencyLevel(ConsistencyLevel serialConsistency)
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).
serialConsistency
- the serial consistency level to set.Statement
object.IllegalArgumentException
- if serialConsistency
is not one of
ConsistencyLevel.SERIAL
or ConsistencyLevel.LOCAL_SERIAL
.public ConsistencyLevel getSerialConsistencyLevel()
See setSerialConsistencyLevel(com.datastax.driver.core.ConsistencyLevel)
for more detail on the serial consistency level.
null
if no serial
consistency level has been specified (through setSerialConsistencyLevel
).
In the latter case, the default serial consistency level will be used.public Statement enableTracing()
Statement
object.public Statement disableTracing()
Statement
object.public boolean isTracing()
true
if this query has tracing enabled, false
otherwise.public abstract ByteBuffer getRoutingKey()
The routing key is optional in that implementers are free to
return null
. The routing key is an hint used for token-aware routing (see
TokenAwarePolicy
), and
if provided should correspond to the binary value for the query
partition key. However, not providing a routing key never causes a query
to fail and if the load balancing policy used is not token aware, then
the routing key can be safely ignored.
null
.public abstract String getKeyspace()
Note that not all query specify on which keyspace they operate on, and
so this method can always return null
. Firstly, some queries do
not operate inside a keyspace: keyspace creation, USE
queries,
user creation, etc. Secondly, even query that operate within a keyspace
do not have to specify said keyspace directly, in which case the
currently logged in keyspace (the one set through a USE
query
(or through the use of Cluster.connect(String)
)). Lastly, as
for the routing key, this keyspace information is only a hint for
token-aware routing (since replica placement depend on the replication
strategy in use which is a per-keyspace property) and having this method
return null
(or even a bogus keyspace name) will never cause the
query to fail.
null
.public Statement setRetryPolicy(RetryPolicy policy)
The default retry policy, if this method is not called, is the one returned by
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.
policy
- the retry policy to use for this query.Statement
object.public RetryPolicy getRetryPolicy()
null
if no query specific
retry policy has been set through setRetryPolicy(com.datastax.driver.core.policies.RetryPolicy)
(in which case
the Cluster retry policy will apply if necessary).public Statement setFetchSize(int fetchSize)
The fetch size controls how much resulting rows will be retrieved simultaneously (the goal being to avoid loading too much results in memory for queries yielding large results). Please note that while value as low as 1 can be used, it is *highly* discouraged to use such a low value in practice as it will yield very poor performance. If in doubt, leaving the default is probably a good idea.
Only SELECT
queries only ever make use of that setting.
Note: Paging is not supported with the native protocol version 1. If
you call this method with fetchSize > 0
and
fetchSize != Integer.MAX_VALUE
and the protocol version is in
use (i.e. if you've force version 1 through Cluster.Builder.withProtocolVersion(int)
or you use Cassandra 1.2), you will get UnsupportedProtocolVersionException
when submitting this statement for execution.
fetchSize
- the fetch size to use. If fetchSize <e; 0
,
the default fetch size will be used. To disable paging of the
result set, use fetchSize == Integer.MAX_VALUE
.Statement
object.public int getFetchSize()
setFetchSize(int)
is used), the default
fetch size will be used.public Statement setPagingState(PagingState pagingState)
This will cause the next execution of this statement to fetch results from a given page, rather than restarting from the beginning.
You get the paging state from a previous execution of the statement (see
ExecutionInfo.getPagingState()
.
This is typically used to iterate in a "stateless" manner (e.g. across HTTP requests):
Statement st = new SimpleStatement("your query");
ResultSet rs = session.execute(st.setFetchSize(20));
int available = rs.getAvailableWithoutFetching();
for (int i = 0; i < available; i++) {
Row row = rs.one();
// Do something with row (e.g. display it to the user...)
}
// Get state and serialize as string or byte[] to store it for the next execution
// (e.g. pass it as a parameter in the "next page" URI)
PagingState pagingState = rs.getExecutionInfo().getPagingState();
String savedState = pagingState.toString();
// Next execution:
// Get serialized state back (e.g. get URI parameter)
String savedState = ...
Statement st = new SimpleStatement("your query");
st.setPagingState(PagingState.fromString(savedState));
ResultSet rs = session.execute(st.setFetchSize(20));
int available = rs.getAvailableWithoutFetching();
for (int i = 0; i < available; i++) {
...
}
The paging state can only be reused between perfectly identical statements (same query string, same bound parameters). Altering the contents of the paging state or trying to set it on a different statement will cause this method to fail.
Note that, due to internal implementation details, the paging state is not portable
across native protocol versions (see the
online documentation
for more explanations about the native protocol).
This means that PagingState
instances generated with an old version won't work
with a higher version. If that is a problem for you, consider using the "unsafe" API (see
setPagingStateUnsafe(byte[])
).
pagingState
- the paging state to set, or null
to remove any state that was
previously set on this statement.Statement
object.PagingStateException
- if the paging state does not match this statement.public Statement setPagingStateUnsafe(byte[] pagingState)
Contrary to setPagingState(PagingState)
, this method takes the "raw" form of the
paging state (previously extracted with ExecutionInfo.getPagingStateUnsafe()
.
It won't validate that this statement matches the one that the paging state was extracted from.
If the paging state was altered in any way, you will get unpredictable behavior from
Cassandra (ranging from wrong results to a query failure). If you decide to use this variant,
it is strongly recommended to add your own validation (for example, signing the raw state with
a private key).
pagingState
- the paging state to set, or null
to remove any state that was
previously set on this statement.Statement
object.public Statement setIdempotent(boolean idempotent)
See isIdempotent()
for more explanations about this property.
idempotent
- the new value.Statement
object.public Boolean isIdempotent()
Idempotence plays a role in speculative executions
.
If a statement is not idempotent, the driver will not schedule speculative
executions for it.
Note that this method can return null
, in which case the driver will default to
QueryOptions.getDefaultIdempotence()
.
By default, this method returns null
for all statements, except for
BuiltStatement
s, where the value will be inferred from the query: if it updates
counters, prepends/appends to a list, or uses a function call or
QueryBuilder.raw(String)
anywhere in an inserted value,
the result will be false
; otherwise it will be true
.
In all cases, calling setIdempotent(boolean)
forces a value that overrides every other mechanism.
null
to use
QueryOptions.getDefaultIdempotence()
.Copyright © 2012–2015. All rights reserved.