[
https://issues.apache.org/jira/browse/CASSANDRA-5062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629047#comment-13629047
]
Jonathan Ellis commented on CASSANDRA-5062:
-------------------------------------------
I ended up inlining the old isEmpty and creating a new one for CAS to use.
Also AbstractSSTableSimpleWriter should be using the "new" isEmpty. The rest I
left alone.
SerializationsTest was failing because I'd inadvertently removed the MUTATION
entry for MS.verbSerializers. (So MessageIn said, oh, serializer == null?
Here's an empty Message for you, and the next Message in the test started
reading partway through the last one.)
Fixed and committed!
> 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
