[jira] Commented: (CASSANDRA-336) Merge batchmutation types and support batched deletes

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-336:
------------------------------------------

the user-level API can be done by adding a ColumnOrSuperColumn type as in CASSANDRA-329 to allow a single unified batch op.

> All I care about is whether a bundle of updates reaches the server atomically

remember atomicity is per row/CF.  if that is what you mean, great.  otherwise you are talking about fairly involved changes to CommitLog.

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