[
https://issues.apache.org/jira/browse/CASSANDRA-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796756#action_12796756
]
Pedro Gomes commented on CASSANDRA-580:
---------------------------------------
I have been following this issue for some time now and I'm curious how will you
deal with reconciliation.
I suppose for the beginning of the discussion that some sort of interface will
be implemented to allow pluggable logic to be added to the server, personalized
scripts were an idea, I have heard.
Is something planned? As a suggestion, Java Scripting API and scripts stored on
Cassandra?
Sorry if I seem hasty, but I will probably work on some dummy implementation as
I need this for my work, and I didn't want to diverge from a future release of
Cassandra.
If you can give me some lights, it would be thankful.
> 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.
