Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.0-ALPHA
-
Component/s: core/search
-
Labels:None
-
Lucene Fields:New
Description
Lucene does all searching/filtering per-segment, today, but there are a number of tests that directly invoke Scorer.scorer or Filter.getDocIdSet on a composite reader.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Forgot to resolve this...
Attached patch.
Only a few query impls were affected, but many tests were directly passing composite readers to the low level API. I added a new helper class SlowMultiReaderWrapper that one can use to wrap an existing composite reader to make it [inefficiently] pretend it's an atomic reader.