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] Commented: (CASSANDRA-336) Merge batchmutation types and support batched deletes
Date Thu, 27 Aug 2009 18:09:59 GMT

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

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

also, adding optional timestamp to ColumnPath is inconsistent with how we use thrift structs.
 we want to make it hard to do The Wrong Thing, and we want to not scatter data around different
structs.  Path is used in gets, so don't add fields that only apply to inserts to it.  And
Path implies a series of names, while [meta]data like timestamp goes in Column/SuperColumn.

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


Mime
View raw message