[
https://issues.apache.org/jira/browse/CASSANDRA-7056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043841#comment-14043841
]
Benedict commented on CASSANDRA-7056:
-------------------------------------
You will read timestamp 2 as the latest value, and will request the latest
value as of that timestamp, which will be 1.5 for C; since 1.5 has to be
visible (if it was written with RAMP transactions and you've seen it, it's
visible) you'll get correct behaviour. If it isn't written with a RAMP
transaction, it's undefined which you see, and that is also correct.
> 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)
