Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1242198459.1243370625703.JavaMail.jira@brutus>
Date: Tue, 26 May 2009 13:43:45 -0700 (PDT)
From: "Jonathan Ellis (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=12713242#action_12713242 ] 

Jonathan Ellis commented on CASSANDRA-48:
-----------------------------------------

... actually, thinking about it a little more, if you are using ZK locks for consistency I don't really see the point of  T&S at all.  Read/write locks are described under shared locks here: http://zookeeper.wiki.sourceforge.net/ZooKeeperRecipes.

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