[
https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905705#action_12905705
]
Jonathan Ellis edited comment on CASSANDRA-580 at 9/2/10 6:35 PM:
------------------------------------------------------------------
As discussed here and in CASSANDRA-1072, this ticket is a dead end for
counting, and the primary use case for classic vector clocks of merging
non-conflicting updates to different fields w/in a value is already handled by
cassandra breaking a row into columns.
Is there a good reason not to close this?
was (Author: jbellis):
As discussed here and in CASSANDRA-1072, this ticket is a dead end for
counting; the primary use case for classic vector clocks of merging
non-conflicting updates to different fields w/in a value is already handled by
cassandra breaking a row into columns.
Is there a good reason not to close this?
> 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.0
>
> Attachments:
> 0001-Add-handler-to-delegate-the-write-protocol-to-a-repl.patch,
> 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.
