jimczi commented on issue #15239: URL: https://github.com/apache/lucene/issues/15239#issuecomment-3365652632
Re-reading the code I think the new BatchScoreBulkScorer should check the score mode before using the minimum score to skip. It's not a bug per say since the minimum score should not be set if the underlying collector is in complete node. What makes this case weird is that multiple collectors with different strategy are used. Following what we do in queries (we check the score mode eagerly before skipping), I think we should do the same in BatchScoreBulkScorer. That won't fix the need to override setMinCompetitiveScore for this specific case since the underlying collector is built with a different score mode. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
