lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rutherglen (JIRA)" <>
Subject [jira] Commented: (LUCENE-1252) Avoid using positions when not all required terms are present
Date Wed, 22 Apr 2009 23:08:47 GMT


Jason Rutherglen commented on LUCENE-1252:

When flexible indexing goes in, users will be able to put data
into the index that allow scorers to calculate a "cheap" score,
collect, then go through and calculate a presumably more
expensive score. 

Would it be good to implement this patch with this sort of more
general framework in mind? 

It seems like this could affect the HitCollector API as we'd
want a more generic way of representing scores than the
primitive "float" we assume now. Aren't we rewriting the
HitCollector APIs right now? Can we implement this change now?

> 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