[
https://issues.apache.org/jira/browse/LUCENE-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739124#action_12739124
]
Michael McCandless commented on LUCENE-1771:
--------------------------------------------
I think we should change the approach here, based on Yonik's last suggestion on
LUCENE-1749, so that QueryWeight.explain receives *both* the top-level Searcher
and the sub-reader, with the docID pre-resolved to that sub-reader. This way
individual queries are not responsible for resolving to sub-readers.
Actually, since QueryWeight is new in 2.9, we can simply make this change w/o
deprecation.
> Using explain may double ram reqs for fieldcaches when using
> ValueSourceQuery/CustomScoreQuery or for ConstantScoreQuerys that use a
> caching Filter.
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-1771
> URL: https://issues.apache.org/jira/browse/LUCENE-1771
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 2.9
>
> Attachments: LUCENE-1771.patch
>
>
--
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]
