[
https://issues.apache.org/jira/browse/LUCENE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1847:
--------------------------------
Description:
PhraseQuery uses IndexReader in explainfor top level stats - as mentioned by
Mike McCandless in LUCENE-1837.
TermQuery uses IndexReader in explain for top level stats
Always been a bug with MultiSearcher, but per segment search makes it worse.
was:
As mentioned by Mike McCandless in LUCENE-1837.
Always been a bug with MultiSearcher, but per segment search makes it worse.
Summary: PhraseQuery/TermQuery use IndexReader specific stats in their
explains (was: PhraseQuery uses IndexReader specific docFreqs in its explain)
Okay - I'm going to use the other issue just to revert the Searcher - more of a
task.
This issue can then be used to track the new work for this bug here.
> PhraseQuery/TermQuery use IndexReader specific stats in their explains
> ----------------------------------------------------------------------
>
> Key: LUCENE-1847
> URL: https://issues.apache.org/jira/browse/LUCENE-1847
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
> Fix For: 2.9
>
>
> PhraseQuery uses IndexReader in explainfor top level stats - as mentioned by
> Mike McCandless in LUCENE-1837.
> TermQuery uses IndexReader in explain for top level stats
> Always been a bug with MultiSearcher, but per segment search makes it worse.
--
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]
