cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelvin Kakugawa (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-580) vector clock support
Date Mon, 19 Jul 2010 01:06:02 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889709#action_12889709
] 

Kelvin Kakugawa commented on CASSANDRA-580:
-------------------------------------------

580 and 1072 are forks of each other.  So, either could be applied first.

Basically, 1072 was built off of the original 580 work.  However, 1072 made a lot of various
improvements to the underlying code.  So, when I brought 580 up to trunk, I incorporated all
of the underlying improvements in 1072, but replaced the counter-specific code w/ the vector
clock implementation.

I believe more ppl are interested in 1072.  So, after that gets committed to trunk, I'll refactor
the above patch to let it be applied on top of 1072.

> 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.


Mime
View raw message