[
https://issues.apache.org/jira/browse/CASSANDRA-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016034#comment-13016034
]
Sylvain Lebresne commented on CASSANDRA-2384:
---------------------------------------------
bq. Might it be worth it to name the Mutation fields/substructs closer to the
action they are performing? "Deletion" and "CounterDeletion" make sense, but
Counter might be better as "Increment"
I don't necessarily disagree but what I don't like with Increment is that it
suggests than you can only use a positive delta. Plus, having 'optional Counter
counter' is coherent with the 'optional ColumnOrSuperColumn
column_or_supercolumn' in a way and after all you're mutating a counter, so ...
Thanks for the stress update.
> Merge Mutation and CounterMutation thrift structure
> ---------------------------------------------------
>
> Key: CASSANDRA-2384
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2384
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Affects Versions: 0.8
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 0.8
>
> Attachments: 0001-Make-thrift-changes-v2.patch,
> 0001-Make-thrift-changes.patch,
> 0002-Merge-CounterMutation-and-Mutation-v2.patch,
> 0002-Merge-CounterMutation-and-Mutation.patch,
> 0003-Update-o.a.c.stress.Stress-for-batch_mutate.txt
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Standard and counter mutation are in 2 different structures, which prevents
> from doing a standard and counter mutation in the same batch_mutate (you have
> to use batch_add for counters). It's probably a good idea to merge
> CounterMutation and Mutation (and simply remove batch_add) to lift that
> limitation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
