Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <880486452.1238730312931.JavaMail.jira@brutus>
Date: Thu, 2 Apr 2009 20:45:12 -0700 (PDT)
From: "Jun Rao (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-48) test-and-set
In-Reply-To: <1830224690.1238712914902.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695224#action_12695224 ] 

Jun Rao commented on CASSANDRA-48:
----------------------------------

We have to be careful about the semantic of test-and-set insert. What happens if the condition is met at some, but not all replicas? If we want to fail the insert in this case, we need to be able to roll back the insert at some replicas.

> test-and-set
> ------------
>
>                 Key: CASSANDRA-48
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-48
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>
> Atomic test-and-set insert operation would be nice: "set value to X but only if the current value is still Y."  This allows a sort of optimistic consistency: perform a GET, then perform test-and-set with the value of that GET as Y.
> I do not think that this requires strong consistency to be useful.

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