[
https://issues.apache.org/jira/browse/CASSANDRA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897006#action_12897006
]
Jonathan Ellis commented on CASSANDRA-1072:
-------------------------------------------
True, you do have to read-before-write for version vectors, but that's a pretty
low price compared to
- losing availability if a single node is down
- a large amount of special-case code for one new op type
I'd very much like to explore the version vector approach in 580 more, before
deciding that we need this extra complexity to achieve reasonable performance.
Because I don't think that will be necessary.
> 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.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.
