[
https://issues.apache.org/jira/browse/LUCENE-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739166#action_12739166
]
Mark Miller commented on LUCENE-1771:
-------------------------------------
bq. This way individual queries are not responsible for resolving to
sub-readers.
... so who is? The user I guess? The only place explain(IndexReader reader, int
doc) appears to be called in Lucene code is with the customscore query. So with
the current patch, you can call these methods and pass the top level reader
like normal, but with this change, you have to get the subreader yourself.
Also, the one internal place that explain(IndexReader reader, int doc) is
called (CustomScoreQuery) would have to pass null for the IndexSearcher.
Something doesn't seem right with this stuff ...
> 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
