[
https://issues.apache.org/jira/browse/CASSANDRA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053853#comment-14053853
]
Jeremiah Jordan commented on CASSANDRA-7056:
--------------------------------------------
bq. 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.
+1 I think we should start with adding RAMP to be used internally. Then once
we have a better idea of what is going on with it, we can explore exposing it
to the end user in a sane way.
> 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)
