[jira] [Updated] (CASSANDRA-15501) Duplicate results with DISTINCT queries in mixed mode 2.1/3.0

2020-04-16 Thread Marcus Eriksson (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Eriksson updated CASSANDRA-15501:

  Fix Version/s: (was: 3.11.x)
 (was: 3.0.x)
 4.0-alpha
 3.11.7
 3.0.21
 2.2.17
  Since Version: 3.0 alpha 1
Source Control Link: 
https://github.com/apache/cassandra/commit/16f639af94f56cdc7145299730278e27a9113e2e
 Resolution: Fixed
 Status: Resolved  (was: Ready to Commit)

committed the duplicate-fix to 3.0 and 3.11 and the dtest + tests to 2.2 and 
trunk, thanks!

> 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: 2.2.17, 3.0.21, 3.11.7, 4.0-alpha
>
>
> 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



[jira] [Updated] (CASSANDRA-15501) Duplicate results with DISTINCT queries in mixed mode 2.1/3.0

2020-04-15 Thread Marcus Eriksson (Jira)


 [ 
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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-15501) Duplicate results with DISTINCT queries in mixed mode 2.1/3.0

2020-01-13 Thread Sam Tunnicliffe (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Tunnicliffe updated CASSANDRA-15501:

Status: Ready to Commit  (was: Review In Progress)

LGTM +1

> 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



[jira] [Updated] (CASSANDRA-15501) Duplicate results with DISTINCT queries in mixed mode 2.1/3.0

2020-01-13 Thread Sam Tunnicliffe (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Tunnicliffe updated CASSANDRA-15501:

Reviewers: Aleksey Yeschenko, Sam Tunnicliffe, Sam Tunnicliffe  (was: 
Aleksey Yeschenko, Sam Tunnicliffe)
   Aleksey Yeschenko, Sam Tunnicliffe, Sam Tunnicliffe  (was: 
Aleksey Yeschenko, Sam Tunnicliffe)
   Status: Review In Progress  (was: Patch Available)

> 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



[jira] [Updated] (CASSANDRA-15501) Duplicate results with DISTINCT queries in mixed mode 2.1/3.0

2020-01-13 Thread Marcus Eriksson (Jira)


 [ 
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



[jira] [Updated] (CASSANDRA-15501) Duplicate results with DISTINCT queries in mixed mode 2.1/3.0

2020-01-13 Thread Marcus Eriksson (Jira)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-15501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

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
   3.0.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
(v8.3.4#803005)

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