You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kelvin Kakugawa (JIRA)" <ji...@apache.org> on 2009/11/25 05:58:40 UTC
[jira] Updated: (CASSANDRA-580) vector clock support
[ https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kelvin Kakugawa updated CASSANDRA-580:
--------------------------------------
Attachment: 580-interface-1-add-vector-clock.diff
proposed vector clock interface
The vector clock is returned by gets and required for insert/remove. I assume that server-side conflict resolution will be implemented, so I only pass back the definitive version of the row. If client-side conflict resolution will be implemented in the future, another data structure will be needed that encapsulates a list of conflicts and, maybe, a summary vector clock to be used for an insert/remove operation that resolves the conflict.
> 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
>
> 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.