Statement (DataStax Java Driver for Apache Cassandra - Binary distribution 2.2.0-rc3 API)

java.lang.Object
- com.datastax.driver.core.Statement

Direct Known Subclasses:

BatchStatement, BoundStatement, RegularStatement, StatementWrapper
```
public abstract class Statement
extends Object
```
An executable query.
This represents either a RegularStatement, a BoundStatement or a BatchStatement along with the querying options (consistency level, whether to trace the query, ...).

Field Summary

Fields
Modifier and Type	Field and Description
`protected Boolean`	`idempotent`
`static ByteBuffer`	`NULL_PAYLOAD_VALUE` A special ByteBuffer value that can be used with custom payloads to denote a null value in a payload map.

Method Summary

All Methods Instance Methods Abstract Methods Concrete Methods
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.
`long`	`getDefaultTimestamp()` The default timestamp 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`	`setDefaultTimestamp(long defaultTimestamp)` Sets the default timestamp for this query (in microseconds since the epoch).
`Statement`	`setFetchSize(int fetchSize)` Sets the query fetch size.
`Statement`	`setIdempotent(boolean idempotent)` Sets whether this statement is idempotent.
`Statement`	`setOutgoingPayload(Map<String,ByteBuffer> payload)` Set the given outgoing payload on this statement.
`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.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Field Detail
  - NULL_PAYLOAD_VALUE
```
public static final ByteBuffer NULL_PAYLOAD_VALUE
```
    A special ByteBuffer value that can be used with custom payloads to denote a null value in a payload map.
  - idempotent
```
protected volatile Boolean idempotent
```
- Method Detail
  - setConsistencyLevel
```
public Statement setConsistencyLevel(ConsistencyLevel consistency)
```
    Sets the consistency level for the query.
    
    Parameters:
    
    consistency - the consistency level to set.
    
    Returns:
    
    this Statement object.
  - getConsistencyLevel
```
public ConsistencyLevel getConsistencyLevel()
```
    The consistency level for this query.
    
    Returns:
    
    the consistency level for this query, or null if no consistency level has been specified (through setConsistencyLevel). In the latter case, the default consistency level will be used.
  - setSerialConsistencyLevel
```
public Statement setSerialConsistencyLevel(ConsistencyLevel serialConsistency)
```
    Sets the serial consistency level for the query. The serial consistency level is only used by conditional updates (so INSERT, UPDATE and DELETE 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).
    
    Parameters:
    
    serialConsistency - the serial consistency level to set.
    
    Returns:
    
    this Statement object.
    
    Throws:
    
    IllegalArgumentException - if serialConsistency is not one of ConsistencyLevel.SERIAL or ConsistencyLevel.LOCAL_SERIAL.
  - getSerialConsistencyLevel
```
public ConsistencyLevel getSerialConsistencyLevel()
```
    The serial consistency level for this query.
    See setSerialConsistencyLevel(com.datastax.driver.core.ConsistencyLevel) for more detail on the serial consistency level.
    
    Returns:
    
    the consistency level for this query, or null if no serial consistency level has been specified (through setSerialConsistencyLevel). In the latter case, the default serial consistency level will be used.
  - enableTracing
```
public Statement enableTracing()
```
    Enables tracing for this query. By default (that is unless you call this method), tracing is not enabled.
    
    Returns:
    
    this Statement object.
  - disableTracing
```
public Statement disableTracing()
```
    Disables tracing for this query.
    
    Returns:
    
    this Statement object.
  - isTracing
```
public boolean isTracing()
```
    Returns whether tracing is enabled for this query or not.
    
    Returns:
    
    true if this query has tracing enabled, false otherwise.
  - getRoutingKey
```
public abstract ByteBuffer getRoutingKey()
```
    Returns the routing key (in binary raw form) to use for token aware routing of this query.
    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.
    
    Returns:
    
    the routing key for this query or null.
  - getKeyspace
```
public abstract String getKeyspace()
```
    Returns the keyspace this query operates on.
    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.
    
    Returns:
    
    the keyspace this query operate on if relevant or null.
  - setRetryPolicy
```
public Statement setRetryPolicy(RetryPolicy policy)
```
    Sets the retry policy to use for this query.
    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.
    
    Parameters:
    
    policy - the retry policy to use for this query.
    
    Returns:
    
    this Statement object.
  - getRetryPolicy
```
public RetryPolicy getRetryPolicy()
```
    Returns the retry policy sets for this query, if any.
    
    Returns:
    
    the retry policy sets specifically for this query or 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).
  - setFetchSize
```
public Statement setFetchSize(int fetchSize)
```
    Sets the query fetch size.
    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(com.datastax.driver.core.ProtocolVersion) or you use Cassandra 1.2), you will get UnsupportedProtocolVersionException when submitting this statement for execution.
    
    Parameters:
    
    fetchSize - the fetch size to use. If fetchSize &lte; 0, the default fetch size will be used. To disable paging of the result set, use fetchSize == Integer.MAX_VALUE.
    
    Returns:
    
    this Statement object.
  - getFetchSize
```
public int getFetchSize()
```
    The fetch size for this query.
    
    Returns:
    
    the fetch size for this query. If that value is less or equal to 0 (the default unless setFetchSize(int) is used), the default fetch size will be used.
  - setDefaultTimestamp
```
public Statement setDefaultTimestamp(long defaultTimestamp)
```
    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).
    Parameters:
    
    defaultTimestamp - the default timestamp for this query (must be strictly positive).
    
    Returns:
    
    this Statement object.
    
    See Also:
    
    Cluster.Builder.withTimestampGenerator(TimestampGenerator)
  - getDefaultTimestamp
```
public long getDefaultTimestamp()
```
    The default timestamp for this query.
    
    Returns:
    
    the default timestamp (in microseconds since the epoch).
  - setPagingState
```
public Statement setPagingState(PagingState pagingState)
```
    Sets the paging state.
    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[])).
    Parameters:
    
    pagingState - the paging state to set, or null to remove any state that was previously set on this statement.
    
    Returns:
    
    this Statement object.
    
    Throws:
    
    PagingStateException - if the paging state does not match this statement.
  - setPagingStateUnsafe
```
public Statement setPagingStateUnsafe(byte[] pagingState)
```
    Sets the paging state.
    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).
    
    Parameters:
    
    pagingState - the paging state to set, or null to remove any state that was previously set on this statement.
    
    Returns:
    
    this Statement object.
  - setIdempotent
```
public Statement setIdempotent(boolean idempotent)
```
    Sets whether this statement is idempotent.
    See isIdempotent() for more explanations about this property.
    
    Parameters:
    
    idempotent - the new value.
    
    Returns:
    
    this Statement object.
  - isIdempotent
```
public Boolean isIdempotent()
```
    Whether this statement is idempotent, i.e. whether it can be applied multiple times without changing the result beyond the initial application.
    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 BuiltStatements, 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.
    
    Returns:
    
    whether this statement is idempotent, or null to use QueryOptions.getDefaultIdempotence().
  - setOutgoingPayload
```
public Statement setOutgoingPayload(Map<String,ByteBuffer> payload)
```
    Set the given outgoing payload on this statement. Each time this statement is executed, this payload will be included in the query request.
    This method makes a defensive copy of the given map, but its values remain inherently mutable. Care should be taken not to modify the original map once it is passed to this method.
    This feature is only available with ProtocolVersion.V4 or above. Trying to include custom payloads in requests sent by the driver under lower protocol versions will result in an UnsupportedFeatureException (wrapped in a NoHostAvailableException).
    
    Parameters:
    
    payload - the outgoing payload to include with this statement, or null to clear any previously entered payload.
    
    Returns:
    
    this Statement object.
    
    Since:
    
    2.2

Class Statement

Field Summary

Method Summary

Methods inherited from class java.lang.Object

Field Detail

NULL_PAYLOAD_VALUE

idempotent

Method Detail

setConsistencyLevel

getConsistencyLevel

setSerialConsistencyLevel

getSerialConsistencyLevel

enableTracing

disableTracing

isTracing

getRoutingKey

getKeyspace

setRetryPolicy

getRetryPolicy

setFetchSize

getFetchSize

setDefaultTimestamp

getDefaultTimestamp

setPagingState

setPagingStateUnsafe

setIdempotent

isIdempotent

setOutgoingPayload