lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul.elschot (JIRA)" <>
Subject [jira] Commented: (LUCENE-370) BooleanQuery assumes everything else implements skipTo
Date Sat, 15 Oct 2005 14:52:45 GMT
    [ ] 

paul.elschot commented on LUCENE-370:

I think all scorers in the trunk implement skipTo() now, so this can be closed.

Paul Elschot

> BooleanQuery assumes everything else implements skipTo
> ------------------------------------------------------
>          Key: LUCENE-370
>          URL:
>      Project: Lucene - Java
>         Type: Bug
>   Components: Search
>     Versions: 1.4
>  Environment: Operating System: other
> Platform: All
>     Reporter: Yonik Seeley
>     Assignee: Lucene Developers

> skipTo seems to be optional functionality on the Scorer class (BooleanScorer
> doesn't implement it).  BooleanQuery.scorer() tests all subclauses using
> "instanceof BooleanQuery" to determine if it can use a ConjunctionScorer that
> requires skipTo functionality.
> This means that any other new Query/Scorer that don't implement skipTo will get
> into trouble when included in a BooleanQuery.
> If skipTo is really optional, then there should be some way of telling by the
> Scorer or the Query in a more generic manner.
> Some options:
> 1) have a "boolean Scorer.hasSkipTo()" method
> 2) have a "boolean Query.hasSkipTo()" method
> 3) remove Scorer.skipTo and have a "public interface ScorerSkipTo{boolean
> skipTo(int doc)}" that scorers may implement

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

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

View raw message