Skip to content
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

Fix MissingValues for Lucene 10 #17647

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

msfroh
Copy link
Collaborator

@msfroh msfroh commented Mar 21, 2025

Description

With the Lucene 10 upgrade, we should not rely on doc values returning NO_MORE_DOCS once they've run out of ords. Instead, we should return a correct value for docValueCount().

Related Issues

Resolves #17628

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

With the Lucene 10 upgrade, we should not rely on doc values returning
NO_MORE_DOCS once they've run out of ords. Instead, we should return a
correct value for docValueCount().

Signed-off-by: Michael Froh <[email protected]>
@msfroh msfroh force-pushed the missing_values_ords branch from 5151667 to 71f1b16 Compare March 21, 2025 00:25
@@ -359,7 +360,8 @@ public long getValueCount() {

@Override
public int docValueCount() {
return Math.max(1, values.docValueCount());
// If we don't have ordinals, then we just have the missing value
return hasOrds ? values.docValueCount() : 1;
}
Copy link
Contributor

@expani expani Mar 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The nextOrd() just below this is also not checking for docValueCount.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's okay. If the caller calls nextOrd() too many times, the behavior is undefined.

Copy link
Contributor

✅ Gradle check result for 71f1b16: SUCCESS

Copy link

codecov bot commented Mar 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.42%. Comparing base (47d3655) to head (71f1b16).
Report is 11 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #17647      +/-   ##
============================================
- Coverage     72.53%   72.42%   -0.11%     
+ Complexity    65826    65756      -70     
============================================
  Files          5311     5311              
  Lines        305073   305073              
  Branches      44243    44245       +2     
============================================
- Hits         221293   220964     -329     
- Misses        65688    65995     +307     
- Partials      18092    18114      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working skip-changelog v3.0.0 Issues and PRs related to version 3.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] SSDV.nextOrd() should not make use of NO_MORE_DOCS
3 participants