You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Max Sanders (JIRA)" <ji...@apache.org> on 2011/01/14 00:00:51 UTC

[jira] Created: (CASSANDRA-1984) Implement "check and set"

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.

[jira] Commented: (CASSANDRA-1984) Implement "check and set"

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981568#action_12981568 ] 

Jonathan Ellis commented on CASSANDRA-1984:
-------------------------------------------

See: CASSANDRA-48

> 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.

[jira] Resolved: (CASSANDRA-1984) Implement "check and set"

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ 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.