[
https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889681#action_12889681
]
Johan Oskarsson commented on CASSANDRA-580:
-------------------------------------------
CASSANDRA-1243 was my somewhat failed attempt to split out code from
CASSANDRA-1072 to make that patch more manageable, but there is not really a
clear cut component to split out so I have canceled that patch. I can close it
for now and reopen if we want to try again. Alternatively create a few smaller
and more focused issues instead. It won't make much of a dent in 1072 though.
The idea is to get CASSANDRA-1072 committed first and then resume work on
CASSANDRA-580. They do both use a lot of the same changes that we have already
committed to Cassandra (clocks, reconciler) and probably share a bit of code
still.
> vector clock support
> --------------------
>
> Key: CASSANDRA-580
> URL: https://issues.apache.org/jira/browse/CASSANDRA-580
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Environment: N/A
> Reporter: Kelvin Kakugawa
> Assignee: Kelvin Kakugawa
> Fix For: 0.7
>
> Attachments: 580-1-Add-ColumnType-as-enum.patch,
> 580-context-v4.patch, 580-counts-wip1.patch, 580-thrift-v3.patch,
> 580-thrift-v6.patch, 580-version-vector-wip.patch
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> Allow a ColumnFamily to be versioned via vector clocks, instead of long
> timestamps. Purpose: enable incr/decr; flexible conflict resolution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
