cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12387) List Append order is wrong
Date Fri, 05 Aug 2016 08:07:20 GMT

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

Sylvain Lebresne commented on CASSANDRA-12387:
----------------------------------------------

No. List append is always based on the server timestamp and does not depend on the client
provided timestamp. Making it depend on the client timestamp if provided would be nice in
principle, but it's unfortunately more complicated than that when there is more than one element
added by a given insert/update, and I worry doing so would create more problems than it solves.

> List Append order is wrong
> --------------------------
>
>                 Key: CASSANDRA-12387
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12387
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: cassandra 2.1.13
>            Reporter: ZhaoYang
>             Fix For: 2.1.16
>
>
> "INSERT INTO collection_type(key,normal_column,list_column) VALUES ('k','value',[ '#293847','#323442'
]);"
> "UPDATE collection_type SET list_column=list_column+'#611987' WHERE key='k`;"
> Using 2.1.7.1 java driver to run Update query, the output is: '#611987', '#293847','#323442'
> Using DevCenter 1.3.1 to execute Update query, result is in correct order: '#293847','#323442',
'#611987'
> The error happened in 3 node cluster. In local, one node is working properly.
> (all Cassandra 2.1.13. )
> Is it related to internal message processing?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message