[
https://issues.apache.org/jira/browse/CASSANDRA-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025880#comment-13025880
]
Pavel Yaskevich edited comment on CASSANDRA-2555 at 4/27/11 4:39 PM:
---------------------------------------------------------------------
USING statement changed to support TIMESTAMP in the following manner for
statements INSERT, UPDATE and BATCH:
{noformat}
USING CONSISTENCY <LEVEL> AND TIMESTAMP <NUMBER>
USING TIMESTAMP <NUMBER> AND CONSISTENCY <LEVEL>
USING TIMESTAMP <NUMBER>
USING CONSISTENCY <LEVEL>
{noformat}
CQL.textile is updated + 3 tests added
was (Author: xedin):
USING statement changed to support TIMESTAMP in the following manner for
statements INSERT, UPDATE and BATCH:
{noformat>
USING CONSISTENCY <LEVEL> AND TIMESTAMP <NUMBER>
USING TIMESTAMP <NUMBER> AND CONSISTENCY <LEVEL>
USING TIMESTAMP <NUMBER>
USING CONSISTENCY <LEVEL>
{noformat}
CQL.textile is updated + 3 tests added
> Explicit timestamp support for CQL
> ----------------------------------
>
> Key: CASSANDRA-2555
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2555
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Reporter: Jonathan Ellis
> Assignee: Pavel Yaskevich
> Fix For: 0.8.1
>
> Attachments: CASSANDRA-2555.patch
>
>
> To make CQL BATCHes useful for the normal purpose of idempotent retries, we
> need to add support for client-supplied timestamps. At a minimum this needs
> to be available for a batch (BEGIN BATCH USING TIMESTAMP 1303743619771318)
> but might also be nice at the statement level (UPDATE ... USING TIMESTAMP
> ...).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
