You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan King (JIRA)" <ji...@apache.org> on 2009/10/19 19:05:59 UTC
[jira] Updated: (CASSANDRA-336) Merge batchmutation types and
support batched deletes
[ https://issues.apache.org/jira/browse/CASSANDRA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan King updated CASSANDRA-336:
--------------------------------
Attachment: v1-0001-CASSANDRA-336.-Thrift-definition-for-batch_mutate.patch
> Merge batchmutation types and support batched deletes
> -----------------------------------------------------
>
> Key: CASSANDRA-336
> URL: https://issues.apache.org/jira/browse/CASSANDRA-336
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.5
> Reporter: Evan Weaver
> Assignee: Evan Weaver
> Fix For: 0.5
>
> Attachments: CASSANDRA-336-code.diff, CASSANDRA-336-thrift.diff, v1-0001-CASSANDRA-336.-Thrift-definition-for-batch_mutate.patch
>
>
> 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.