[
https://issues.apache.org/jira/browse/CASSANDRA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053843#comment-14053843
]
Aleksey Yeschenko commented on CASSANDRA-7056:
----------------------------------------------
Linking to
https://issues.apache.org/jira/browse/CASSANDRA-7489?focusedCommentId=14053825&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14053825
to not repeat myself.
TL;DR - logged batches are playing a different role than RAMP transactions are
supposed to, so one can't replace another.
This doesn't mean that we can't add RAMP transactions as a separate feature, of
course. What I'm arguing for is that RAMP-powered global indexes and
RAMP-powered materialized views do cover the vast majority of cases where you'd
'manually' use RAMP otherwise, and we shouldn't expose them as a standalone
thing just because we can.
> 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)
