[
https://issues.apache.org/jira/browse/CASSANDRA-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816129#comment-13816129
]
Aleksey Yeschenko commented on CASSANDRA-4775:
----------------------------------------------
bq. 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 ?
No more overcounts b/c of internal replays. Read on write becomes explicit and
non-optional, with replicate_on_write gone.
bq. How is this going ?
In progress. The hard part is maintaining backward compatibility, and
compatibility during a rolling upgrade. Working on this at the moment, and it's
not trivial at all.
> 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)
