[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737254#action_12737254
]
Mark Miller commented on LUCENE-1749:
-------------------------------------
bq. If the CustomScoreQuery class(es) push the FieldCache sage into the
subReaders during scoring, then shouldn't the explain methods do the same
thing? it definitely seems like a bug if getting score explanation from a query
causes your memory footprint to double.
It *should* do the same thing - but thats sticky. If you push explain to the
sub readers, you will get why it scored as it did for each subreader - not one
top level explain. I won't deny its kind of bug - but I'm not sure at the
moment what the best way to address it is. I'll look into the possibility of
pushing the fieldcache access to the subreaders while leaving everything else
at the top reader - I have no thoughts about the feasibility of that at the
moment though. I guess it might be doable.
> FieldCache introspection API
> ----------------------------
>
> Key: LUCENE-1749
> URL: https://issues.apache.org/jira/browse/LUCENE-1749
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Hoss Man
> Priority: Minor
> Fix For: 2.9
>
> Attachments: fieldcache-introspection.patch, LUCENE-1749.patch,
> LUCENE-1749.patch, LUCENE-1749.patch, LUCENE-1749.patch, LUCENE-1749.patch,
> LUCENE-1749.patch
>
>
> FieldCache should expose an Expert level API for runtime introspection of the
> FieldCache to provide info about what is in the FieldCache at any given
> moment. We should also provide utility methods for sanity checking that the
> FieldCache doesn't contain anything "odd"...
> * entries for the same reader/field with different types/parsers
> * entries for the same field/type/parser in a reader and it's subreader(s)
> * etc...
--
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]
