[
https://issues.apache.org/jira/browse/CASSANDRA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909241#action_12909241
]
Jonathan Ellis commented on CASSANDRA-1072:
-------------------------------------------
A major concern is that the clocks are part of the API and schema. So if we
commit this as-is then we have several possible scenarios:
#clock change gets in before 0.7.0 and everything is fine
#clock change isn't ready for 0.7.0 and we block 0.7.0 for it
#clock change isn't ready for 0.7.0, we release anyway, and break compatibility
w/ the next release
#clock change isn't ready for 0.7.0 so we postpone it until 0.8 (thus having to
maintain both versions until 0.7 is obsolete)
2-4 are not acceptable and while I know you have the best of intentions to
finish it right away, the rest of 0.7.0 is shaping up rapidly and it just
doesn't look like a good risk to me.
> 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, 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.
