lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] Updated: (LUCENE-1847) PhraseQuery/TermQuery use IndexReader specific stats in their explains
Date Mon, 24 Aug 2009 12:59:59 GMT


Mark Miller updated LUCENE-1847:

    Attachment: LUCENE-1847.patch

rough draft - works as the fix, but could use some polish.

And what to do about back compat - because its just explain output, I don't think its a huge
but if you overrode idf(Collection terms, Searcher searcher) or idf(Term term, Searcher searcher)
Sim, right now they wouldn't be called for TermQuery and PhraseQuery. An override of float
idf(int docFreq, int numDocs)
would still be taken into account though.

> PhraseQuery/TermQuery use IndexReader specific stats in their explains
> ----------------------------------------------------------------------
>                 Key: LUCENE-1847
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>            Priority: Minor
>             Fix For: 2.9
>         Attachments: LUCENE-1847.patch
> 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:
For additional commands, e-mail:

View raw message