-
As discussed in IndexSearcher should handle the case when the executor rejects the execution of a task (unavailability of threads?).
---
### Legacy Jira details
[LUCENE-8989](https://issues.apach…
-
In LUCENE-8855, there is a discussion around adding memory accounting capabilities to QueryVisitor to allow estimation of memory consumption by queries.'
This Jira tracks the effort
---
### Legac…
-
Now that we have QueryVisitor, the rewrite functionality should belong there, since rewrite is essentially a recursive visitation of underlying queries, which sounds exactly as what QueryVisitor is de…
-
It would be good to be able to uniquely identify LeafReaderContext objects associated within a single IndexSearcher. This would allow storing of metadata around segments, such as demonstrated in #1954…
-
CheckIndex checks the order of fields read from the FieldsEnum for the posting reader. Since we do not explicitly sort or use a sorted data structure to represent keys (atleast explicitly), and no Fie…
-
TopDocsCollector is tightly coupled to the notion of priority queue, which is not necessarily a good abstraction to have since the collector really just needs an interface to iterate on and hold docID…
-
CheckIndex checks the order of fields read from the FieldsEnum for the posting reader. Since we do not explicitly sort or use a sorted data structure to represent keys (atleast explicitly), and no Fie…
-
While doing some perf tests, I realised that FieldComparators inherently maintain implicit priority queues for maintaining the sorted order of documents for the given sort order. This is wasteful espe…
-
While discussing improvements in relevance of fuzzy queries with @jimczi, the topic of how to measure impact of changes to relevance of common queries came up. While a non trivial effort, having such …
-
It would be good to be able to uniquely identify LeafReaderContext objects associated within a single IndexSearcher. This would allow storing of metadata around segments, such as demonstrated in https…