cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14567) CQL query returns different results in 2.2.5 and 3.0.15
Date Mon, 16 Jul 2018 15:10:00 GMT

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

Benedict commented on CASSANDRA-14567:
--------------------------------------

This is a little mind melting.  But it seems like whatever semantics we pick need to be consistent
across all possible clusterings - for both least surprise/confusion for developers, and so
that MVs/2i's provide consistent results.

AFAICT the 3.0 semantics provide this, and are intuitive, whereas the 2.2 do not, and are
not.

> CQL query returns different results in 2.2.5 and 3.0.15
> -------------------------------------------------------
>
>                 Key: CASSANDRA-14567
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14567
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Dikang Gu
>            Priority: Major
>
> During our 2.2.5 to 3.0.15 upgrade, we find the a cql query returns different results
in 2.2.5 and 3.0.15, here is a unit test to reproduce it, [https://gist.github.com/DikangGu/e538ed2de22b74e49b8dd43f7093a996]
>  
> In C* 2.2.5, it returns all 4 rows: *[Row[1, 10, 0, 1], Row[1, 10, 10, 2], Row[1, 1,
0, 3], Row[1, 1, 10, 4]]*
> While in C* 3.0.15, it only returns 2 rows to client: *[Row[1, 10, 0, 1], Row[1, 1, 10,
4]]*
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message