fix: Fixing secondary index read perf for V1 layout#14149
Merged
Conversation
Collaborator
yihua
pushed a commit
that referenced
this pull request
Oct 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe the issue this Pull Request addresses
While adding V2 support for Secondary index, we added a refactoring or V1 read path which resulted in some perf regression. Fixing the V1 read of secondary index. We saw > 10X perf regression w/ the code block of interest.
Summary and Changelog
While adding V2 support for Secondary index, we added a refactoring or V1 read path which resulted in some perf regression. Fixing the V1 read of secondary index.
Impact
Perf numbers on par or better compared to reading with 1.0.2 hudi.
Risk Level
low
Documentation Update
Contributor's checklist