[
https://issues.apache.org/jira/browse/CASSANDRA-4775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783065#comment-13783065
]
Aleksey Yeschenko commented on CASSANDRA-4775:
----------------------------------------------
[~nff] Right, the set-based approach has its advantages, but they don't
outweigh the disadvantages, unfortunately.
bq. Remove the replicate_on_write option and switch to a locked/retryable RMW.
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).
bq. Provide a pluggable way to implement commutative types, with a PN-counter
implementation.
Assuming that you are talking about a separate counter implementation from the
primary one for now, I don't have an issue with it, I think. But the pluggable
CRDTs are way out of scope for the 2.1 (that's supposed to be a
stabilizing/tech debt release). Consider opening a separate 3.0 ticket for
that, maybe?
> 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)
