Synopsis:
USE <KEYSPACE>;
A USE
statement consists of the USE
keyword, followed by a valid keyspace name. Its purpose is to assign the per-connection, current working keyspace. All subsequent keyspace-specific actions will be performed in the context of the supplied value.
Synopsis:
SELECT [FIRST N] [REVERSED] <SELECT EXPR> FROM <COLUMN FAMILY> [USING <CONSISTENCY>]
[WHERE <CLAUSE>] [LIMIT N];
@@ -39,4 +60,4 @@
DROP
statements result in the immediate, irreversible removal of keyspace and column family namespaces.
... USING <CONSISTENCY> ...
Consistency level specifications are made up the keyword USING
, followed by a consistency level identifier. Valid consistency levels are as follows:
CONSISTENCY ZERO
CONSISTENCY ONE
(default)CONSISTENCY QUORUM
CONSISTENCY ALL
CONSISTENCY DCQUORUM
CONSISTENCY DCQUORUMSYNC
Terms are used in statements to specify things such as keyspaces, column families, indexes, column names and values, and keyword arguments. The rules governing term specification are as follows:
'apple'
).carrot
).100
).1438fc5c-4ff6-11e0-b97f-0026c650d722
). Terms which do not conform to these rules result in an exception.
How column name/value terms are interpreted is determined by the configured type.
type | term |
---|---|
ascii | Any string which can be decoded using ASCII charset |
text / varchar | Any string which can be decoded using UTF8 charset |
uuid | Standard UUID string format (hyphen-delimited hex notation) |
uuid | Standard UUID string format (hyphen-delimited hex notation) |
uuid | The string now , to represent a type-1 (time-based) UUID with a date-time component based on the current time |
uuid | Numeric value representing milliseconds since epoch |
uuid | An iso8601 timestamp |
bigint | Numeric value capable of fitting in 8 bytes |
varint | Numeric value of arbitrary size |
bytea | Hex-encoded strings (converted directly to the corresponding bytes) |
Versioning of the CQL language adheres to the Semantic Versioning guidelines. Versions take the form X.Y.Z where X, Y, and Z are integer values representing major, minor, and patch level respectively. There is no correlation between Cassandra release versions and the CQL language version.
version | description |
---|---|
Patch | The patch version is incremented when bugs are fixed. |
Minor | Minor version increments occur when new, but backward compatible, functionality is introduced. |
Major | The major version must be bumped when backward incompatible changes are introduced. This should rarely (if ever) occur. |
Tue, 22 Mar 2011 18:10:28 -0700 - Eric Evans <eevans@rackspace.com> * Initial version, 1.0.0 -\ No newline at end of file +