[
https://issues.apache.org/jira/browse/CASSANDRA-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695476#action_12695476
]
Jonathan Ellis commented on CASSANDRA-48:
-----------------------------------------
Like I said on the ML, in that case you would have to do a read that waits for
all replicas. Which will hurt availability but I don't see any alternative.
Again, this isn't intended going to provide strong consistency. You can still
come up with failure scenarios where inconsistent data could be read
temporarily. I'm not sure if it's going to be useful given that.
> test-and-set
> ------------
>
> Key: CASSANDRA-48
> URL: https://issues.apache.org/jira/browse/CASSANDRA-48
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
>
> Atomic test-and-set insert operation would be nice: "set value to X but only
> if the current value is still Y." This allows a sort of optimistic
> consistency: perform a GET, then perform test-and-set with the value of that
> GET as Y.
> I do not think that this requires strong consistency to be useful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
