https://issues.apache.org/jira/i#browse/SOLR-7816 raised to track this.
Yes, the issue only surfaces if queryResultsCache is configured and filterCache
is not configured. I agree, this should not affect (m)any real users, just
points towards opportunity to split/refactor somehow - i stumbled acr
timeAllowed parameter ignored edge-case bug
> (queryResultsCache=yes,filterCache=no)
> --
>
> Key: SOLR-7816
> URL: https://issues.apache.org/jira/browse/SOLR-7816
>
uest:
https://github.com/apache/lucene-solr/pull/192
SOLR-7816: timeAllowed parameter ignored edge-case bug?
for https://issues.apache.org/jira/i#browse/SOLR-7816
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bloomberg/lucene-
Christine Poerschke created SOLR-7816:
-
Summary: timeAllowed parameter ignored edge-case bug
(queryResultsCache=yes,filterCache=no)
Key: SOLR-7816
URL: https://issues.apache.org/jira/browse/SOLR-7816
: In the scenario outlined below, the second run's timeAllowed parameter
: is unexpectedly ignored. Could this be intentionally so somehow (q vs.
: fq processing?, Collector vs. LeafCollector?, DocList vs. DocSet?), or
: is it an edge-case bug?
Based on your description (didn't re-review the c
Hello.
Was looking at
https://github.com/apache/lucene-solr/blob/trunk/solr/core/src/java/org/apache/solr/search/SolrIndexSearcher.java
code to better understand the various getDoc... methods and how collectors are
combined.
In the scenario outlined below, the second run's timeAllowed paramete
