[
https://issues.apache.org/jira/browse/CASSANDRA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593475#comment-13593475
]
Cristian Opris commented on CASSANDRA-5062:
-------------------------------------------
BTW, last time I looked into it, Cassandra still didn't guarantee monotonic
read or read after write even with qourum read/write consistency level.
There is still a window (even if small) where a qourum read catches the
replicas in a partial write state (A,A,B) with B timestamp > A timestamp
and the result depends on which majority I read, correct ? So we shouldn't rely
on that for paxos, considering the paxos is meant to give true
consistency read (hopefully)
> Support CAS
> -----------
>
> Key: CASSANDRA-5062
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5062
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Fix For: 2.0
>
> Attachments: half-baked commit 1.jpg, half-baked commit 2.jpg,
> half-baked commit 3.jpg
>
>
> "Strong" consistency is not enough to prevent race conditions. The classic
> example is user account creation: we want to ensure usernames are unique, so
> we only want to signal account creation success if nobody else has created
> the account yet. But naive read-then-write allows clients to race and both
> think they have a green light to create.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
