[
https://issues.apache.org/jira/browse/CASSANDRA-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-6857:
-----------------------------------
Description: The paging for RangeSliceCommand only support the case where
we count CQL3 rows . However, in the case of SELECT DISTINCT, we do actually
want to use the "count partitions, not CQL3 row" path and that's currently
broken when the paging commands are used (this was first reported on the [Java
driver JIRA|https://datastax-oss.atlassian.net/browse/JAVA-288] and there is a
reproduction script there). (was: The paging for RangeSliceCommand only
support the case where we count CQL3 rows . However, in the case of SELECT
DISTINCT, we do actually want to use the "count partitions, not CQL3 row" path
and that's currently broken when the paging commands are used (this was first
reported on the [Java driver
JIRA|thttps://datastax-oss.atlassian.net/browse/JAVA-288] and there is a
reproduction script there).)
> SELECT DISTINCT with a LIMIT is broken by paging
> ------------------------------------------------
>
> Key: CASSANDRA-6857
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6857
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 2.0.7
>
> Attachments: 6857-2.0.txt, 6857-2.1.txt
>
>
> The paging for RangeSliceCommand only support the case where we count CQL3
> rows . However, in the case of SELECT DISTINCT, we do actually want to use
> the "count partitions, not CQL3 row" path and that's currently broken when
> the paging commands are used (this was first reported on the [Java driver
> JIRA|https://datastax-oss.atlassian.net/browse/JAVA-288] and there is a
> reproduction script there).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
