[
https://issues.apache.org/jira/browse/CASSANDRA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748453#action_12748453
]
Jonathan Ellis commented on CASSANDRA-336:
------------------------------------------
+ for(RowMutation row_mutation : row_mutations)
+ {
+ doInsert(consistency_level, row_mutation);
}
this isn't what you want; you want to have StorageProxy dispatch the inserts in
parallel so you don't have N times the latency when you operate on N keys.
goffinet's patches in CASSANDRA-70 (to be merged RSN as soon as I get my thrift
crap working) illustrate this approach.
> 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-code.diff, CASSANDRA-336-thrift.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.
