cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-336) Merge batchmutation types and support batched deletes
Date Fri, 18 Dec 2009 21:55:18 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-336:
-------------------------------------

    Affects Version/s:     (was: 0.5)

> 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
>            Reporter: Evan Weaver
>            Assignee: Jeff Hodges
>             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, CASSANDRA-336-v3-Adding-support-for-batch-mutations.patch,
CASSANDRA-336-v4-Adding-support-for-batch-mutations.patch, CASSANDRA-336-v5-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.


Mime
View raw message