[ https://issues.apache.org/jira/browse/CASSANDRA-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946598#comment-13946598 ]
Michael Shuler commented on CASSANDRA-6893: ------------------------------------------- Applied the patch to cassandra-2.0 HEAD and the test case now gives me a clean 1-1000 series. +1 > Unintended update with conditional statement > -------------------------------------------- > > Key: CASSANDRA-6893 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6893 > Project: Cassandra > Issue Type: Bug > Environment: Ubuntu Precise 64bit / Cassandra 2.0.6 > Reporter: Suguru Namura > Assignee: Sylvain Lebresne > Fix For: 2.0.7 > > Attachments: 6893.txt, ConcurrentCASUpdate.java > > > After updated to 2.0.6, I have encountered the strange behavior of > conditional updates. > When I executed CQL like UPDATE test SET value = ? WHERE id = ? IF value = ? > in concurrent, sometimes cassandra returns true even if value is not > satisfied the condition. > I have attached the program which reproduce this issue. The program works > fine in cassandra 2.0.5. But it seems that resets values while execution in > 2.0.6. -- This message was sent by Atlassian JIRA (v6.2#6252)