fix(scan): preserve partition group order - #692
Merged
JingsongLi merged 2 commits intoAug 8, 2026
Conversation
XiaoHongbo-Hope
marked this pull request as ready for review
August 7, 2026 15:53
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.
Purpose
PaimonTableScangrouped manifest entries by partition and bucket in aHashMap. Iterating that map produced a process-dependent split order, so LIMIT pushdown could retain different split groups for the same manifest entries.Use nested
IndexMaps to preserve first-seen partition order and first-seen bucket order within each partition, mirroring Java's nestedLinkedHashMaps. This makes split planning deterministic without promising query result order when no ordering is requested.Tests
table_scan::tests: 82 passedcargo fmt --all -- --checkcargo clippy -p paimon --lib --tests -- -D warnings