[
https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Kakugawa updated CASSANDRA-580:
--------------------------------------
Attachment: 580-version-vector-wip.patch
bringing 580 up to trunk (g...@714eab0c4079276eefcdd5a1d8d9ca7b225c9f80)
TODO:
1) modify version vector node ids to use a unique, per-connection id (thanks
Cliff Moon and Andy Gross for pointing this out as an improvement)
- note: see Riak's implementation, which derives unique client ids based on
erlang process id.
pros: less replica coordination wrt node ids.
necessary evil: must add timestamps to version vector tuples and prune the
version vector (based on time).
2) modify tuple format
- add timestamp (to allow version vector pruning)
- shorten count type to be int, instead of long (node ids will updated for a
much shorter period of time)
> 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.
