mirror of https://github.com/apache/cassandra
Merge branch 'cassandra-2.1' into trunk
This commit is contained in:
commit
30f438ff4d
|
|
@ -89,6 +89,7 @@ Merged from 1.2:
|
|||
* Fix snapshot repair not snapshotting coordinator itself (CASSANDRA-6713)
|
||||
* Support negative timestamps for CQL3 dates in query string (CASSANDRA-6718)
|
||||
* Avoid NPEs when receiving table changes for an unknown keyspace (CASSANDRA-5631)
|
||||
* Fix bootstrapping when there is no schema (CASSANDRA-6685)
|
||||
|
||||
|
||||
2.0.5
|
||||
|
|
|
|||
|
|
@ -542,7 +542,7 @@ h4(#updateOptions). @<options>@
|
|||
|
||||
The @UPDATE@ and @INSERT@ statements allows to specify the following options for the insertion:
|
||||
* @TIMESTAMP@: sets the timestamp for the operation. If not specified, the current time of the insertion (in microseconds) is used. This is usually a suitable default.
|
||||
* @TTL@: allows to specify an optional Time To Live (in seconds) for the inserted values. If set, the inserted values are automatically removed from the database after the specified time. Note that the TTL concerns the inserted values, not the column themselves. This means that any subsequent update of the column will also reset the TTL (to whatever TTL is specified in that update). By default, values never expire.
|
||||
* @TTL@: allows to specify an optional Time To Live (in seconds) for the inserted values. If set, the inserted values are automatically removed from the database after the specified time. Note that the TTL concerns the inserted values, not the column themselves. This means that any subsequent update of the column will also reset the TTL (to whatever TTL is specified in that update). By default, values never expire. A TTL of 0 or a negative one is equivalent to no TTL.
|
||||
|
||||
|
||||
h3(#deleteStmt). DELETE
|
||||
|
|
|
|||
Loading…
Reference in New Issue