Repository navigation
format_table: fix writes when partition columns are reordered - #1111
Merged
JingsongLi merged 1 commit intoOct 12, 2026
Merged
Conversation
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
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.
Summary
Fix Format Table writes when a partition column is not the first field in the table schema. The writer previously combined full-schema column indices with partition-only field metadata, which could panic with an out-of-bounds access.
Changes
Testing
cargo test -p paimon-datafusion --test rest_format_table_dmlcargo clippy -p paimon-datafusion --test rest_format_table_dml -- -D warningscargo fmt --all -- --check