[
https://issues.apache.org/jira/browse/LUCENE-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2597:
---------------------------------------
Attachment: LUCENE-2597.patch
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.
> Query scorers should not use MultiFields
> ----------------------------------------
>
> Key: LUCENE-2597
> URL: https://issues.apache.org/jira/browse/LUCENE-2597
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.0
>
> Attachments: LUCENE-2597.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
