cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Shuler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6893) Unintended update with conditional statement
Date Mon, 24 Mar 2014 22:49:45 GMT

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

Michael Shuler commented on CASSANDRA-6893:
-------------------------------------------

If I understand the test case correctly, I should get (as I do in 2.0.5) a nice clean 1-1000
update series of:
{noformat}
creating keyspace
creating table
insert default value
APPLIED 1
APPLIED 2
APPLIED 3
  <snip 4-997>
APPLIED 998
APPLIED 999
APPLIED 1000
FINAL VALUE IS 1000
{noformat}

In 2.0.6, I get random series of 1-X, ending in a random FINAL VALUE.  Using the 2.0.6 and
2.0.5 git tags, this bisects to:

{noformat}
b09d876914ad9c9fdf1af35cf48cdb98c27bbf32 is the first bad commit
commit b09d876914ad9c9fdf1af35cf48cdb98c27bbf32
Author: Sylvain Lebresne <sylvain@datastax.com>
Date:   Thu Jan 9 18:44:21 2014 +0100

    Add static columns in CQL3
    
    patch by slebresne; reviewed by iamaleksey for CASSANDRA-6561

:100644 100644 4fffb9acefb1fbb9172b5ed99bbeaa0d537b967b bbacc4d83babaf4880ab9f175509dc5fb88d6461
M      CHANGES.txt
:040000 040000 7ac6d76f9b69884c07342eed468327a2da1403ad aa93d5ffb85ce62b3cbe8d6d3e987cd9f147a26e
M      doc
:040000 040000 7d15a4bf52f49b432b297a4e22554e40cabb6035 3fcc45ef24616cf2026b84059409a249d65cb9fd
M      src
{noformat}

> 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: Michael Shuler
>             Fix For: 2.0.7
>
>         Attachments: 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)

Mime
View raw message