Marcus Eriksson updated CASSANDRA-15501:
     Bug Category: Parent values: Correctness(12982)Level 1 values: Transient 
Incorrect Response(12987)
       Complexity: Normal
      Component/s: Legacy/Core
    Discovered By: Adhoc Test
    Fix Version/s: 3.11.x
        Reviewers: Aleksey Yeschenko, Sam Tunnicliffe
         Severity: Normal
           Status: Open  (was: Triage Needed)

> 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

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

Reply via email to