You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/11/30 20:51:58 UTC

[jira] [Commented] (CASSANDRA-4775) Counters 2.0

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

Jonathan Ellis commented on CASSANDRA-4775:
-------------------------------------------

One possibility:

During write each increment is a separate increment -- that is, a separate wide row cell / cql3 row. But during reads, each node sums everything locally and sends that.

If we do that, merging counts becomes a local problem: you can say that each node merges locally once the counter is older than gc_grace_seconds (or maybe a separate configuration setting).  This could be done during compaction.
                
> Counters 2.0
> ------------
>
>                 Key: CASSANDRA-4775
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4775
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Arya Goudarzi
>              Labels: counters
>             Fix For: 1.3
>
>
> The existing partitioned counters remain a source of frustration for most users almost two years after being introduced.  The remaining problems are inherent in the design, not something that can be fixed given enough time/eyeballs.
> Ideally a solution would give us
> - similar performance
> - less special cases in the code
> - potential for a retry mechanism

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira