Affects Version/s: 5.2.1, 5.4, 6.0
Fix Version/s: 5.3.1
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.