You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alain RODRIGUEZ (JIRA)" <ji...@apache.org> on 2013/11/04 15:09:32 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=13812852#comment-13812852 ]
Alain RODRIGUEZ commented on CASSANDRA-4775:
--------------------------------------------
{quote}Remove the replicate_on_write option and switch to a locked/retryable RMW.{quote}
What will this imply for the final user ? No more over-counts due to retry, no more read on write ? Any disadvantage switching to those locked RMW ?
Counters are very useful, but also really hard to handle because of their specific characteristics. I hope that some of them will be removed here.
{quote}This (+some optimizations) is what we are going for in 2.1, and will be ready soon-ish (returning back to this after one issue).{quote}
How is this going ?
> 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
> Assignee: Aleksey Yeschenko
> Labels: counters
> Fix For: 2.1
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)