[
https://issues.apache.org/jira/browse/CASSANDRA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Hodges updated CASSANDRA-336:
----------------------------------
Attachment: CASSANDRA-336-v2-Adding-support-for-batch-mutations.patch
This batch adds support for batched mutations.
This change includes an addition of Deletion, Mutation and batch_mutate to the
thrift-generated API. It allows for the insertion or deletion of specific
columns or supercolumns over multiple keys and multiple keyspaces.
It does not support slices as they turned out to be a total PITA. We would have
had to make changes to the way slices were handled down to the ColumnFamily
level.
> 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: Tim Huske
> Fix For: 0.9
>
> Attachments: 336-thrift.patch, CASSANDRA-336-code.diff,
> CASSANDRA-336-thrift.diff,
> CASSANDRA-336-v2-Adding-support-for-batch-mutations.patch,
> 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.
