[
https://issues.apache.org/jira/browse/LUCENE-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713918#action_12713918
]
Shai Erera commented on LUCENE-1252:
------------------------------------
I must admit that I read the issue briefly, and so my proposal below may be
irrelevant.
But it sounds to me like for the above example we'd want to use
ConjunctionScorer to first iterate on both Scorers (PhraseScorer?) until they
agree, and only then call Collector.collect(), which will call Scorer.score()
in return (if a scoring collector is used).
Alternatively, we can implement a FilterCollector (if there isn't one already)
which impls its collect(int doc) by first determining if a document is a match,
and then call a given Collector, which will proceed with collecting and scoring.
> Avoid using positions when not all required terms are present
> -------------------------------------------------------------
>
> Key: LUCENE-1252
> URL: https://issues.apache.org/jira/browse/LUCENE-1252
> 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
