[
https://issues.apache.org/jira/browse/CASSANDRA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977965#action_12977965
]
Sylvain Lebresne commented on CASSANDRA-1936:
---------------------------------------------
You're right, don't know what I have smoked. Actually I was still thinking in
the context of 1546, where it's always a replica that 'apply' the update (since
the coordinator simply forward the update to a replica if its not one).
That being said, I do plan to introduce this part 1546, because it allowed to
rehabilitate the consistency levels. So maybe I should do that before, in which
case I think the method here would work.
Still, curious to see your patch. But I'll admit that I was actually happy to
get rid of the updateCommutativeType logic.
> Fit partitioned counter directly into CounterColumn.value
> ----------------------------------------------------------
>
> Key: CASSANDRA-1936
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1936
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 0.8
>
> Attachments:
> 0001-Put-partitioned-counter-directly-in-column-value.patch
>
>
> The current implementation of CounterColumn keeps both the partitioned
> counter and the total value of the counter (that is, the sum of the parts of
> the partitioned counter).
> This waste space and this requires the code to keep both representation in
> sync. This ticket propose to remove the total value from the representation
> and to only calculate it when returning the value to the client.
> NOTE: this breaks the on-disk file format (for counters)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
