cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CASSANDRA-1984) Implement "check and set"
Date Thu, 13 Jan 2011 23:14:46 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-1984.
---------------------------------------

    Resolution: Won't Fix

You can't implement CAS in an eventually consistent system.

> Implement "check and set"
> -------------------------
>
>                 Key: CASSANDRA-1984
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1984
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Max Sanders
>             Fix For: 0.7.1
>
>
> When fetching data from cassandra you should ask for a hash value for the stored value.
Then when updating a value it should be possible to submit this hash value and only update
the data when the hash key is still the same.
> This way you can be sure that the data was not changed on this node.
> It is the same as the memcached CAS Feature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message