[
https://issues.apache.org/jira/browse/CASSANDRA-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-2384:
----------------------------------------
Attachment: 0002-Merge-CounterMutation-and-Mutation-v4.patch
0001-Make-thrift-changes-v4.patch
Wow, don't know why I attached that half backed v3, sorry about that.
Attaching v4 that does check that the timestamp is set for non commutative CF
and actually set it to server time for commutative CF. I also reverted small
changed that were made to validateDeletion previously to accomodate
CounterDeletion.
> 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-v3.patch, 0001-Make-thrift-changes-v4.patch,
> 0001-Make-thrift-changes.patch,
> 0002-Merge-CounterMutation-and-Mutation-v2.patch,
> 0002-Merge-CounterMutation-and-Mutation-v3.patch,
> 0002-Merge-CounterMutation-and-Mutation-v4.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
