[
https://issues.apache.org/jira/browse/LUCENE-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739182#action_12739182
]
Mark Miller commented on LUCENE-1771:
-------------------------------------
bq. which brings up another point... isn't a back-compat break too (since
Weight is not a QueryWeight)? IndexSearcher.Explanation explain(QueryWeight
weight, int doc) throws IOException;
nice catch.
Hmmm - so scorer.explain(doc) would need to be deprecated cause it would need
to take a Searcher (too avoid putting it on QueryWeight) and the sub-reader -
and again this would need to be solved (like the current patch) a Query at a
time.
> 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]
