You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nimi Wariboko Jr. (JIRA)" <ji...@apache.org> on 2016/02/10 22:40:18 UTC

[jira] [Commented] (CASSANDRA-8216) Select Count with Limit returns wrong value

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

Nimi Wariboko Jr. commented on CASSANDRA-8216:
----------------------------------------------

Is there a way to emulate the old behavior? The prestodb (https://prestodb.io/) query engine was using this query to estimate the number of rows in the table (perhaps incorrectly), and now that {{count(\*)}} accurately returns everything its slow and incorrect.

> Select Count with Limit returns wrong value
> -------------------------------------------
>
>                 Key: CASSANDRA-8216
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8216
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Benjamin Lerer
>              Labels: qa-resolved
>             Fix For: 2.2.0 beta 1
>
>
> The dtest cql_tests.py:TestCQL.select_count_paging_test is failing on trunk HEAD but not 2.1-HEAD.
> The query {code} select count(*) from test where field3 = false limit 1; {code} is returning 2, where obviously it should only return 1 because of the limit. This may end up having the same root cause of #8214, I will be bisecting them both soon.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)