test: add mixed-format rename column coverage#365
Open
liujiwen-up wants to merge 1 commit into
Open
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.
Purpose
Linked issue: close #258
Add Spark-generated consistency coverage for schema evolution with
RENAME COLUMNacross mixed file formats.Old files are written with the original physical column name, while files written after the rename use the new column name. Rust readers should expose the current column name and read values by field id.
Brief change log
schema_evolution_rename_columnto the Spark provisioning script.RENAME COLUMN.Tests
cargo fmt: passedcargo test -p paimon arrow::schema_evolution: passedcargo test -p paimon-integration-tests --test read_tables --no-run: passedAPI and Format
No public API or storage format changes.
Documentation
No documentation update required.