[
https://issues.apache.org/jira/browse/CASSANDRA-13130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871978#comment-15871978
]
Mikhail Krupitskiy commented on CASSANDRA-13130:
------------------------------------------------
Thank you for the clarification!
Such behaviour looks like not intuitive - will be very useful to have the
description somewhere in Cassandra's docs.
1) Are there any plans to make the behaviour more intuitive like "the second
value will win because it comes last"?
2) How the following query will work (does an order matter?)?
{code}UPDATE t SET listColumn[2] = 8, listColumn = 7 + listColumn WHERE id =
1;{code}
3) Is there a general recommendation not to combine several updates to one
column in the single query?
> 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
> Assignee: Benjamin Lerer
> Priority: Trivial
>
> 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.15#6346)
