[
https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784638#action_12784638
]
Kelvin Kakugawa commented on CASSANDRA-580:
-------------------------------------------
Thanks Stu for the lead.
I studied the Interval Tree Clocks paper and it looks promising. Let me work
out the algorithm, so that we can investigate its implementation in Cassandra.
Having said the above, I think we should re-do the "clock" aspect of the
interface and make it an opaque context object (like Dynamo). We pass it out
to clients on a read, and when they update a given value they pass back the
context that they're updating. I'm not sure if we want to extend the concept
so far as to make existing timestamps just a special case of an opaque context,
though.
> 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
> Attachments: 580-interface-1-add-vector-clock.diff,
> 580-interface-2-add-vector-clock.diff, 580-thrift-v3.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.
