[
https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796805#action_12796805
]
Kelvin Kakugawa commented on CASSANDRA-580:
-------------------------------------------
For the initial server-side reconciliation, we'll probably adopt an approach
similar to the way custom ColumnFamily comparators are specified.
It might help to refer to:
http://wiki.apache.org/cassandra/StorageConfiguration
In particular, the section called, "Keyspaces and ColumnFamilies," where they
discuss compareWith and how you can extend
org.apache.cassandra.db.marshal.AbstractType to use your own ColumnFamily
comparator.
For the initial implementation to get this out the door, we won't support a
javascript API. However, I'm open to suggestions. It probably would be nice
to support a high-level scripting language for certain components.
> 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
> Attachments: 580-context-v1.patch, 580-context-v2.patch,
> 580-context-v3.patch, 580-interface-1-add-vector-clock.diff,
> 580-interface-2-add-vector-clock.diff, 580-thrift-v3.patch,
> 580-thrift-v4.patch, 580-thrift-v5.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.
