|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
getValues, getValues, toString
disableTracing, enableTracing, getConsistencyLevel, getDefaultTimestamp, getFetchSize, getRetryPolicy, getSerialConsistencyLevel, isIdempotent, isTracing, setConsistencyLevel, setDefaultTimestamp, setFetchSize, setIdempotent, setPagingState, setPagingStateUnsafe, setRetryPolicy, setSerialConsistencyLevel
public String getQueryString()
Statementobjects. For example,
Statementobjects carry numerous protocol-level settings, such as the
consistency levelto use, or the
idempotence flag, among others. None of these settings will be included in the resulting query string. Similarly, if values have been set on this statement because it has bind markers, these values will not appear in the resulting query string. Note: the consistency level was conveyed at CQL level in older versions of the CQL grammar, but since CASSANDRA-4734 it is now a protocol-level setting and consequently does not appear in the query string.
public ByteBuffer getValues(ProtocolVersion protocolVersion)
null) are not supported with the native protocol version 1: you will get an
UnsupportedProtocolVersionExceptionwhen submitting one if version 1 of the protocol is in use (i.e. if you've force version 1 through
Cluster.Builder.withProtocolVersion(com.datastax.driver.core.ProtocolVersion)or you use Cassandra 1.2).
protocolVersion- the protocol version in which the returned values must be serialized for.
nullif there is no such values.
public boolean hasValues()
public String getKeyspace()
null. Firstly, some queries do not operate inside a keyspace: keyspace creation,
USEqueries, 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
USEquery (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.
public ByteBuffer getRoutingKey()
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.