[
https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782296#action_12782296
]
Jonathan Ellis commented on CASSANDRA-580:
------------------------------------------
Yes, that's how you'd have to change it. I'd rather not; it would get messy.
(If we do server-side resolution we could still conceivably support both
"classic" columnfamilies and vector clocked ones in the same Column and
SuperColumn objects, just differing in their clock/timestamp field. But if we
have to potentially store multiple versions of a column in a single row for the
vector clock version, then I think that is diverging too far and we'd have to
split the implementation. Remember that a classic ColumnFamily object just has
a hash of its columns by name.)
> 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.
