cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evan Weaver (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-336) Merge batchmutation types and support batched deletes
Date Wed, 26 Aug 2009 00:09:59 GMT

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

Evan Weaver updated CASSANDRA-336:
----------------------------------

    Attachment: CASSANDRA-336-deletes-in-BatchMutation-2-gen-java.diff

> 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: Evan Weaver
>         Attachments: CASSANDRA-336-deletes-in-BatchMutation-2-code.diff, CASSANDRA-336-deletes-in-BatchMutation-2-gen-java.diff
>
>
> 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