-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] SSDV.nextOrd() should not make use of NO_MORE_DOCS #17628
Comments
Thanks for opening the issue @rishabhmaurya Please assign this issue to me. Was able to reproduce with
Error
|
Looks like there's also an occurrence in I think the implementation of OpenSearch/server/src/main/java/org/opensearch/search/aggregations/support/MissingValues.java Lines 317 to 328 in 8447737
I believe the correct implementation of We also have some redundant checks where we're checking both
Those redundant checks aren't a problem AFAIK, but we should probably just check |
Describe the bug
Lucene 10 makes it illegal to call SortedSetDocValues#nextOrd() more than#docValueCount() times for the currently-positioned doc.
https://github.com/apache/lucene/blob/e7f9bc837e419672d9bfc829d01e643df667e9d4/lucene/core/src/java/org/apache/lucene/index/SortedSetDocValues.java#L36
Remove all occurrences of
SSDV.nextOrd() != NO_MORE_DOCS
and replace with use of SSDV.docValuesCount() like in #17626I consider this as a blocker to OpenSearch 3.0 which is making use of lucene 10.
Related component
Search
To Reproduce
This was causing flakiness in MultiOrdinalsTests as encountered in PR #17446 with failure https://build.ci.opensearch.org/job/gradle-check/54686/testReport/junit/org.opensearch.index.fielddata.ordinals/MultiOrdinalsTests/testRandomValues/
Expected behavior
Remove all occurrences of
SSDV.nextOrd() != NO_MORE_DOCS
and replace with use of SSDV.docValuesCount()Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: