[ https://issues.apache.org/jira/browse/CASSANDRA-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-15501: ---------------------------------------- Test and Documentation Plan: new upgrade test & cci runs Status: Patch Available (was: Open) [patch|https://github.com/krummas/cassandra/commits/marcuse/distinct_duplicates] [tests|https://circleci.com/workflow-run/46f204cc-0a6c-4fa7-9e14-73b10e3afb20] > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org