lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (Updated) (JIRA)" <>
Subject [jira] [Updated] (LUCENE-1252) Avoid using positions when not all required terms are present
Date Tue, 20 Mar 2012 16:03:38 GMT


Michael McCandless updated LUCENE-1252:

    Labels: gsoc2012 lucene-gsoc-12  (was: )
> Avoid using positions when not all required terms are present
> -------------------------------------------------------------
>                 Key: LUCENE-1252
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Wish
>          Components: core/search
>            Reporter: Paul Elschot
>            Priority: Minor
>              Labels: gsoc2012, lucene-gsoc-12
> In the Scorers of queries with (lots of) Phrases and/or (nested) Spans, currently next()
and skipTo() will use position information even when other parts of the query cannot match
because some required terms are not present.
> This could be avoided by adding some methods to Scorer that relax the postcondition of
next() and skipTo() to something like "all required terms are present, but no position info
was checked yet", and implementing these methods for Scorers that do conjunctions: BooleanScorer,
PhraseScorer, and SpanScorer/NearSpans.

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


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

View raw message