[ https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888789#action_12888789 ]
Kazuki Aranami commented on CASSANDRA-580: ------------------------------------------ Hello. I recognize that I am very important after implementation of this Vector Clock thought about the architecture. Is the work of Vector Clock stopping? I am concerned about the influence on road map. 0.7 roadmap http://www.mail-archive.com/d...@cassandra.apache.org/msg00404.html There is such a site, too. itclocks http://code.google.com/p/itclocks/ thanks! > 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 > > 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.