[ https://issues.apache.org/jira/browse/CASSANDRA-8216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947210#comment-14947210
]
Jeremiah Jordan commented on CASSANDRA-8216:
--------------------------------------------
[~blerer] not sure Inagree with the assessment that count was wrong before. This is how count
has interacted with LIMIT since it has existed in CQL. I don't think we should be changing
this behavior lightly.
> 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)
|