|Constructor and Description|
|Modifier and Type||Method and Description|
Returns the keyspace this query operates on.
Returns the query string for this statement.
Returns the routing key (in binary raw form) to use for token aware routing of this query.
The values to use for this statement.
Whether or not this statement has values, that is if
disableTracing, enableTracing, getConsistencyLevel, getDefaultTimestamp, getFetchSize, getRetryPolicy, getSerialConsistencyLevel, isIdempotent, isTracing, setConsistencyLevel, setDefaultTimestamp, setFetchSize, setIdempotent, setOutgoingPayload, setPagingState, setPagingStateUnsafe, setRetryPolicy, setSerialConsistencyLevel
public String getQueryString()
public ByteBuffer getValues()
Note: Values for a RegularStatement (i.e. if this method does not return
null) are not supported with the native protocol version 1: you
will get an
UnsupportedProtocolVersionException when submitting
one if version 1 of the protocol is in use (i.e. if you've force version
Cluster.Builder.withProtocolVersion(com.datastax.driver.core.ProtocolVersion) or you use
SimpleStatement.SimpleStatement(String, Cluster, Object...)
public boolean hasValues()
public 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,
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
(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
null (or even a bogus keyspace name) will never cause the
query to fail.
public ByteBuffer getRoutingKey()
The routing key is optional in that implementers are free to
null. The routing key is an hint used for token-aware routing (see
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.
Copyright © 2012–2015. All rights reserved.