cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8216) Select Count with Limit returns wrong value
Date Thu, 08 Oct 2015 12:41:26 GMT


Benjamin Lerer commented on CASSANDRA-8216:

I completly agree that I should have put an entry in the {{NEWS.txt}}.

To be honest, I forgot that I had changed the behaviour.
When [~aholmber] reported CASSANDRA-10380, I tested {{2.2}} and found out the same behavior
than {{2.1}}. I concluded wrongly that the change was coming from CASSANDRA-8099 ([~slebresne]
you were right as always).

Now, the problem is that, after I changed the code, another change caused the code to revert
to the old behavior. I have not found which one yet but it impact only {{2.2}}. So I need
to fix that issue and backport the CASSANDRA-10380 change to {{2.2}}.


> Select Count with Limit returns wrong value
> -------------------------------------------
>                 Key: CASSANDRA-8216
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Benjamin Lerer
>              Labels: qa-resolved
>             Fix For: 2.2.0 beta 1
> The dtest 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

View raw message