public abstract class SchemaStatement extends RegularStatement
SchemaBuilder.idempotent, NULL_PAYLOAD_VALUE| Constructor and Description | 
|---|
SchemaStatement()  | 
| Modifier and Type | Method and Description | 
|---|---|
String | 
getKeyspace()
Returns the keyspace this query operates on. 
 | 
String | 
getQueryString()
Returns the query string for this statement. 
 | 
ByteBuffer | 
getRoutingKey()
Returns the routing key (in binary raw form) to use for token aware
 routing of this query. 
 | 
ByteBuffer[] | 
getValues()
The values to use for this statement. 
 | 
boolean | 
hasValues()
Whether or not this statement has values, that is if  
getValues
 will return null or not. | 
toStringdisableTracing, enableTracing, getConsistencyLevel, getDefaultTimestamp, getFetchSize, getRetryPolicy, getSerialConsistencyLevel, isIdempotent, isTracing, setConsistencyLevel, setDefaultTimestamp, setFetchSize, setIdempotent, setOutgoingPayload, setPagingState, setPagingStateUnsafe, setRetryPolicy, setSerialConsistencyLevelpublic String getQueryString()
RegularStatementgetQueryString in class RegularStatementpublic ByteBuffer[] getValues()
RegularStatement
 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
 1 through Cluster.Builder.withProtocolVersion(com.datastax.driver.core.ProtocolVersion) or you use
 Cassandra 1.2).
getValues in class RegularStatementSimpleStatement.SimpleStatement(String, Cluster, Object...)public boolean hasValues()
RegularStatementgetValues
 will return null or not.hasValues in class RegularStatementfalse if RegularStatement.getValues() returns null, true
 otherwise.public String getKeyspace()
Statement
 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.
getKeyspace in class Statementnull.public ByteBuffer getRoutingKey()
Statement
 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.
getRoutingKey in class Statementnull.Copyright © 2012–2015. All rights reserved.