Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 21 Mar 2014 17:47:43 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12701500.1394812058904.119844.1395424063481@arcas>
In-Reply-To: <JIRA.12701500.1394812058904@arcas>
References: <JIRA.12701500.1394812058904@arcas>
Subject: [jira] [Commented] (CASSANDRA-6857) SELECT DISTINCT with a LIMIT is
 broken by paging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943295#comment-13943295 ] 

Tyler Hobbs commented on CASSANDRA-6857:
----------------------------------------

Thanks.  I thought something might be missing; that makes sense.

It looks like some a ColumnFamilyStoreTest method needs to be updated for the 2.0 patch to compile (you just need to add the countCQL3Rows argument to two makeExtendedFilter() calls).  Other than that, +1.

> 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-v2.txt, 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)