cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7056) Add RAMP transactions
Date Wed, 25 Jun 2014 18:04:25 GMT


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:
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core
>            Reporter: Tupshin Harper
>            Priority: Minor
> We should take a look at [RAMP|]
transactions, and figure out if they can be used to provide more efficient LWT (or LWT-like)

This message was sent by Atlassian JIRA

View raw message