Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Tue, 8 Sep 2015 18:44:46 +0000 (UTC)
From: "Yonik Seeley (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12860529.1440887013000.282027.1441737886270@Atlassian.JIRA>
In-Reply-To: <JIRA.12860529.1440887013000@Atlassian.JIRA>
References: <JIRA.12860529.1440887013000@Atlassian.JIRA>
 <JIRA.12860529.1440887013581@arcas>
Subject: [jira] [Updated] (SOLR-7990) timeAllowed is returning wrong results
 on the same query submitted with different timeAllowed limits
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SOLR-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yonik Seeley updated SOLR-7990:
-------------------------------
    Attachment: SOLR-7990.patch

Here's the latest patch with the rewritten ExitableDirectoryReaderTest.  It fails without the patch and passes with it.

> timeAllowed is returning wrong results on the same query submitted with different timeAllowed limits
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7990
>                 URL: https://issues.apache.org/jira/browse/SOLR-7990
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.2.1, Trunk, 5.4
>            Reporter: Erick Erickson
>            Assignee: Yonik Seeley
>         Attachments: SOLR-7990.patch, SOLR-7990.patch, SOLR-7990.patch, SOLR-7990.patch, SOLR-7990_filterFix.patch
>
>
> William Bell raised a question on the user's list. The scenario is
> > send a query that exceeds timeAllowed
> > send another identical query with larger timeAllowed that does NOT time out
> The results from the second query are not correct, they reflect the doc count from the first query.
> It apparently has to do with filter queries being inappropriately created and re-used. I've attached a test case that illustrates the problem.
> There are three tests here. 
> testFilterSimpleCase shows the problem.
> testCacheAssumptions is my hack at what I _think_ the states of the caches should be, but has a bunch of clutter so I'm Ignoring it for now. This should be un-ignored and testFilterSimpleCase removed when there's any fix proposed. The assumptions may not be correct though.
> testQueryResults shows what I think is a problem, the second call that does NOT exceed timeAllowed still reports partial results.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org