Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
None
-
New
Description
I found the issue while building the release candidate for 8.4. There is a rare bug in WANDScorer that occurs when a block is ignored because the sum of the maximum scores is less than the minimum competitive score. In that case WANDScorer advances until it finds a block where the sum of the maximum scores is greater than the minimum competitive score. Then it pops clauses from the tail until the maximum score of the tail gets smaller than the minimum competitive score, advances these clauses beyond the current target, and treats the smallest doc ID as the next candidate. This is where the bug lies: sometimes this candidate will be beyond the current block and WANDScorer won't update maximum scores of other clauses. In this case it might skip over hits thinking that they can't have a competitive score when in fact they could.