You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mikhail Krupitskiy (JIRA)" <ji...@apache.org> on 2017/01/17 17:41:26 UTC
[jira] [Created] (CASSANDRA-13130) Strange result of several list
updates in a single request
Mikhail Krupitskiy created CASSANDRA-13130:
----------------------------------------------
Summary: Strange result of several list updates in a single request
Key: CASSANDRA-13130
URL: https://issues.apache.org/jira/browse/CASSANDRA-13130
Project: Cassandra
Issue Type: Bug
Reporter: Mikhail Krupitskiy
Priority: Critical
Let's assume that we have a row with the 'listColumn' column and value \{1,2,3,4\}.
For me it looks logical to expect that the following two pieces of code will ends up with the same result but it isn't so.
Code1:
{code}
UPDATE t SET listColumn[2] = 7, listColumn[2] = 8 WHERE id = 1;
{code}
Expected result: listColumn=\{1,2,8,4\}
Actual result: listColumn=\{1,2,7,8,4\}
Code2:
{code}
UPDATE t SET listColumn[2] = 7 WHERE id = 1;
UPDATE t SET listColumn[2] = 8 WHERE id = 1;
{code}
Expected result: listColumn=\{1,2,8,4\}
Actual result: listColumn=\{1,2,8,4\}
So the question is why Code1 and Code2 give different results?
Looks like Code1 should give the same result as Code2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)