[
https://issues.apache.org/jira/browse/CASSANDRA-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957499#comment-13957499
]
Sylvain Lebresne commented on CASSANDRA-6893:
---------------------------------------------
Fair enough, the test should be handling timeouts. But outside of that, I was
wrong when I said that this was a test to reproduce that issue since that issue
only happen with prepared statements and the dtest wasn't using them. So
anyway, I pushed a fix of the paxos dtest so that it does uses a prepared
statement and properly handles timeouts. The test doesn't pass on cassandra-2.0
(there is no {{errors}] but the value is incorrect), but does pass with the
patch.
> 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)
