You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Peter Bailis (JIRA)" <ji...@apache.org> on 2014/06/25 01:36:28 UTC

[jira] [Commented] (CASSANDRA-7056) Add RAMP transactions

    [ https://issues.apache.org/jira/browse/CASSANDRA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042848#comment-14042848 ] 

Peter Bailis commented on CASSANDRA-7056:
-----------------------------------------

As I mentioned at the Next-Generation Cassandra Conference, I'm happy to get the ball rolling on an implementation of RAMP in Cassandra.

To reiterate a few points from the NGCC, I think RAMP could provide some useful isolation guarantees for Cassandra's Atomic Batch operations (either none of the updates will be visible, or all are visible) as well as provide the basis for "consistent" global secondary index updates in Cassandra-6477. I've posted my slides from the NGCC on SpeakerDeck; the Cassandra-specific implementation details start on transition number 287.
https://speakerdeck.com/pbailis/scalable-atomic-visibility-with-ramp-transactions

I have some time to hack on this and am willing to work on a patch and/or hammer out the Cassandra-specific design with you all over JIRA or otherwise!



> Add RAMP transactions
> ---------------------
>
>                 Key: CASSANDRA-7056
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7056
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>            Reporter: Tupshin Harper
>            Priority: Minor
>
> We should take a look at [RAMP|http://www.bailis.org/blog/scalable-atomic-visibility-with-ramp-transactions/] transactions, and figure out if they can be used to provide more efficient LWT (or LWT-like) operations.



--
This message was sent by Atlassian JIRA
(v6.2#6252)