Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1025573587.1249316114795.JavaMail.jira@brutus>
Date: Mon, 3 Aug 2009 09:15:14 -0700 (PDT)
From: "Evan Weaver (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Created: (CASSANDRA-336) Merge batchmutation types and
 support batched deletes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Merge batchmutation types and support batched deletes
-----------------------------------------------------

                 Key: CASSANDRA-336
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-336
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Evan Weaver


I need all possible mutations to be able to be bundled into a generic batchMutation, and sent as one operation.

In the absence of database constraints, this gives you all the benefits of transactions with none of the implementation pain. All I care about is whether a bundle of updates reaches the server atomically, mitigating issues with unreliable client VMs, and allowing the client to "roll back" a set of operations by merely discarding the batch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.