[
https://issues.apache.org/jira/browse/CASSANDRA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904771#action_12904771
]
Johan Oskarsson commented on CASSANDRA-1072:
--------------------------------------------
Admittedly there are tradeoffs to the approach used in 1072+1397 as outlined in
previous comments. As long as users are aware of these constraints there are
plenty of use cases, demonstrated by the interest on the mailing list. Similar
to how eventual consistency may prevent some applications but are good enough
for plenty of others.
Are there any specific code changes we can make to the patch in order to make
it commit worthy?
> Increment counters
> ------------------
>
> Key: CASSANDRA-1072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1072
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Johan Oskarsson
> Assignee: Kelvin Kakugawa
> Attachments: CASSANDRA-1072-2.patch, CASSANDRA-1072-2.patch,
> CASSANDRA-1072.patch, CASSANDRA-1072.patch, Incrementcountersdesigndoc.pdf
>
>
> Break out the increment counters out of CASSANDRA-580. Classes are shared
> between the two features but without the plain version vector code the
> changeset becomes smaller and more manageable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
