lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <>
Subject [jira] Commented: (LUCENE-912) DisjunctionMaxScorer.skipTo has bug that keeps it from skipping
Date Fri, 08 Jun 2007 16:03:26 GMT


Doron Cohen commented on LUCENE-912:

I think you're right, and actually wondered about the same thing while verifying that fix:
"why return in next() but not in skipTo()?" - I believe this is the right thing to do because
at the initialization (ie in add(Scorer)) each added sub-scorer is advanced to its first match.
So the first time that next() is called, sub-scorers are already "on the right spot", and
not so for the first time skipTo() is called, because skipTo does not necessarily goes to
the first match.

> DisjunctionMaxScorer.skipTo has bug that keeps it from skipping
> ---------------------------------------------------------------
>                 Key: LUCENE-912
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 2.1
>            Reporter: Hoss Man
>            Assignee: Doron Cohen
>             Fix For: 2.2
>         Attachments: checkTwoCallsToScore.patch, checkTwoCallsToScore.patch, dismax_skipto.patch,
> as reported on the mailing list, DisjunctionMaxScorer.skipTo is broken if called before
next in some situations...

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