cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5062) Support CAS
Date Mon, 08 Apr 2013 21:58:17 GMT


Jonathan Ellis commented on CASSANDRA-5062:

bq. Also, I think we're lacking something around reads and around CL.SERIAL. I think we at
least need to support CL.SERIAL reads, that would have to go through paxos (so they play inProgress
values). But I would a relatively big fan to also allow a (non-SERIAL) CL in cas() that would
be applied to the final commit of the cas write

Yes, I think I mentioned both of these as "stuff that is missing."  Would rather make them
follow-on tickets.
> Support CAS
> -----------
>                 Key: CASSANDRA-5062
>                 URL:
>             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
> "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:

View raw message