cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Tata (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-336) Merge batchmutation types and support batched deletes
Date Mon, 03 Aug 2009 18:19:14 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738476#action_12738476
] 

Sandeep Tata commented on CASSANDRA-336:
----------------------------------------

The write-to-commitlog would have to be atomic (ie, a single log record) for the batchMutation

You can always ignore/stop at a malformed commitlog record during replay.
I can see how this'd be useful if you were trying to implement a secondary index.


> 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.


Mime
View raw message