[
https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782290#action_12782290
]
Jonathan Ellis commented on CASSANDRA-580:
------------------------------------------
As Stu points out, if the client has to resolve writes, you can no longer
compact without involving the client. This is a big big lose. +1 pluggable
server-side conflict resolution from me.
(This doesn't have to be complicated; just allow a class name to be specified
per-CF like we do for CompareWith.)
Also, I think you can make a good case that this is a better stylistic fit for
Cassandra, which tries to support "dumb" clients more than Dynamo did.
> 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
> 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.
