lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-914) Scorer.skipTo(current) remains on current for some scorers
Date Thu, 07 Jun 2007 00:04:25 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502153
] 

Hoss Man commented on LUCENE-914:
---------------------------------

my gut says we should fix the Impls and leave the spec the way it is ... less risk of irate
clients 2 years down the road wondering why their custom Query classes no longer work in boolean
queries because we: a) relaxed the spec; b) made optimizations in BooleanQuery to take advantage
of the relaxation.

> Scorer.skipTo(current) remains on current for some scorers
> ----------------------------------------------------------
>
>                 Key: LUCENE-914
>                 URL: https://issues.apache.org/jira/browse/LUCENE-914
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>            Reporter: Doron Cohen
>            Priority: Minor
>
> Background in http://www.nabble.com/scorer.skipTo%28%29-contr-tf3880986.html
> It appears that several scorers do not strictly follow the spec of Scorer.skipTo(n),
and skip to current location remain in current location whereas the spec says: "beyond current".

> We should (probably) either relax the spec or fix the implementations.

-- 
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message