Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sat, 1 Sep 2012 08:37:08 +1100 (NCT)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <818795697.25045.1346449028125.JavaMail.jiratomcat@arcas>
In-Reply-To: <1369532753.8053.1344961838499.JavaMail.jiratomcat@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-4542) add atomic_batch_mutate
 method
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aleksey Yeschenko edited comment on CASSANDRA-4542 at 9/1/12 8:35 AM:
----------------------------------------------------------------------

CASSANDRA-4542-4544.diff contains two commits - the one previously attached here, #4544, and adds atomic_batch_commit to thrift interface.
What's missing (from this patch): 4543, flush optimization.
                
      was (Author: iamaleksey):
    CASSANDRA-4542-4544.diff contains to commits - the one previously attached here, #4544, and adds atomic_batch_commit to thrift interface.
What's missing (from this patch): 4543, flush optimization.
                  
> add atomic_batch_mutate method
> ------------------------------
>
>                 Key: CASSANDRA-4542
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4542
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2.1
>
>         Attachments: CASSANDRA-4542-4544.diff, CASSANDRA-4542.patch
>
>
> atomic_batch_mutate will have the same parameters as batch_mutate, but will write to the batchlog before attempting distribution to the batch rows' replicas.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira