lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4607) Add estimateDocCount to DocIdSetIterator
Date Thu, 14 Mar 2013 18:16:14 GMT


Robert Muir commented on LUCENE-4607:

The patch might be hard to apply due to the svn replace Stefan. I plan on doing final checks
on it and committing it today.

Really its silly lucene doesnt have this for our scorers already, since e.g. textbook IR formulas
make use of this stuff. 

We can open followup issues to improve the other scorers logic (FilteredQuery, SpanNearQuery,
etc). I only did the obvious 
conjunction one so we get the logic of ConjunctionTermScorer across any arbitrary scorers.

Just gimme a few hours, sorry for the delay :)
> Add estimateDocCount to DocIdSetIterator
> ----------------------------------------
>                 Key: LUCENE-4607
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>    Affects Versions: 4.0
>            Reporter: Simon Willnauer
>             Fix For: 4.3
>         Attachments: LUCENE-4607.patch, LUCENE-4607.patch
> this is essentially a spinnoff from LUCENE-4236
> We currently have no way to make any decsision on how costly a DISI is neither when we
apply filters nor when we build conjunctions in BQ. Yet we have most of the information already
and can easily expose them via a cost API such that BS and FilteredQuery can apply optimizations
on per segment basis.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message