lucene-dev mailing list archives

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


Robert Muir updated LUCENE-4607:

    Attachment: LUCENE-4607.patch

Patch updated to trunk (as Stefan needs this for LUCENE-4571).

I carefully reviewed all these costs and also integrated it into spans. Though these queries
(e.g. nearquery) dont yet use it, they should.

The only query i changed was to make ConjunctionTermScorer algorithm our ConjunctionScorer,
sorting subscorers on cost (which is docFreq in the all terms case).

> 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