You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2020/04/15 13:13:00 UTC
[jira] [Updated] (CASSANDRA-15501) Duplicate results with DISTINCT
queries in mixed mode 2.1/3.0
[ https://issues.apache.org/jira/browse/CASSANDRA-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-15501:
----------------------------------------
Reviewers: Aleksey Yeschenko, Alex Petrov, Sam Tunnicliffe (was: Aleksey Yeschenko, Sam Tunnicliffe)
> Duplicate results with DISTINCT queries in mixed mode 2.1/3.0
> -------------------------------------------------------------
>
> Key: CASSANDRA-15501
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15501
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
>
> When a client switches coordinator from a 2.1 node to a 3.0 node it sends a 2.1 paging state to the 3.0 node. The 2.1 {{PagingState}} does not have {{remainingInPartition}} so on the 3.0 side we default this to Integer.MAX_VALUE. This value is then used to decide if the lastKey should be included in the result.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org