lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-1252) Avoid using positions when not all required terms are present
Date Fri, 24 Apr 2009 20:10:30 GMT


Michael McCandless commented on LUCENE-1252:

Right, I think this is more about determining whether a doc is a hit or not, than about how
to compute its score.

I think somehow the scorer needs to return 2 scorers that share the underlying iterators.
 The first scorer simply checks "AND"-ness with all other required terms, and only if the
doc passes those are the positional/payloads/anything-else-expensive consulted.

> Avoid using positions when not all required terms are present
> -------------------------------------------------------------
>                 Key: LUCENE-1252
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Wish
>          Components: Search
>            Reporter: Paul Elschot
>            Priority: Minor
> 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.
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