You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Doron Cohen (JIRA)" <ji...@apache.org> on 2011/01/26 22:46:49 UTC
[jira] Commented: (LUCENE-914) Scorer.skipTo(current) remains on
current for some scorers
[ https://issues.apache.org/jira/browse/LUCENE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987244#action_12987244 ]
Doron Cohen commented on LUCENE-914:
------------------------------------
Checking if this issue can be resolved.
There were quite a few changes in this code:
* in LUCENE-584 skipTo was moved to DISI
* in LUCENE-1614 skipTo was replaced by advance() and the javadocs were refreshed.
Current javadocs of DISI.advance() are almost accurate to me, and I think this can be fixed by adding one more (first) note to the method, like this:
{code}
* <b>NOTE:</b> this method is intended for use with <code>target > current</code>,
* otherwise it is not guaranteed to advance beyond current.
{code}
> 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
> Attachments: lucene-914.patch
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org