Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 29 Apr 2011 17:37:03 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <642624638.12087.1304098623332.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <653968731.278.1303754703150.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2555) Explicit timestamp support for
 CQL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027091#comment-13027091 ] 

Hudson commented on CASSANDRA-2555:
-----------------------------------

Integrated in Cassandra #872 (See [https://builds.apache.org/hudson/job/Cassandra/872/])
    

> 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-v2.patch, 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