[
https://issues.apache.org/jira/browse/CASSANDRA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054206#comment-14054206
]
Jonathan Ellis commented on CASSANDRA-7056:
-------------------------------------------
Because without read support RAMP doesn't actually give you anything more than
logged batches. If I update tables X and Y in the same RAMP batch, then I do
concurrent queries against X and Y, I have no isolation guarantees because the
coordinator doesn't know to check both places.
But, I think we can add read support pretty easily. "Just" extend BATCH syntax
to allow SELECT. JDBC has had the concept of multiple resultsets for ages.
> 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)
