[
https://issues.apache.org/jira/browse/CASSANDRA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053849#comment-14053849
]
Benedict commented on CASSANDRA-7056:
-------------------------------------
bq. logged batches are playing a different role than RAMP transactions are
supposed to, so one can't replace another.
Isn't the point of logged batches here to ensure that the trigger write
succeeds if the write generating it does? In which case can we not upgrade a
trigger-involving-write to _all_ be a part of the same RAMP transaction? That
either commits or not as one.
> 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)
