You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/07/09 06:42:06 UTC

[jira] [Comment Edited] (CASSANDRA-7056) Add RAMP transactions

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

Jonathan Ellis edited comment on CASSANDRA-7056 at 7/9/14 4:40 AM:
-------------------------------------------------------------------

bq. TL;DR - logged batches are playing a different role than RAMP transactions are supposed to, so one can't replace another.

But RAMP transactions (with logged commit so we don't need to rely purely on "read repair" for coordinator failure mid-commit) give you a superset of logged batches.  So I don't see a need to introduce new syntax for the former.


was (Author: jbellis):
bq. TL;DR - logged batches are playing a different role than RAMP transactions are supposed to, so one can't replace another.

But RAMP transactions give you a superset of logged batches.  So I don't see a need to introduce new syntax for the former.

> 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)