test: cover mixed-format reorder column reads#366
Open
liujiwen-up wants to merge 1 commit into
Open
Conversation
7c64a66 to
ca012be
Compare
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: #258
Add focused Spark-provisioned integration coverage for mixed-format schema evolution reads after
ALTER COLUMN ... FIRST/AFTER.This PR intentionally covers only the reorder/move-column case to avoid overlapping with #354, which covers mixed-format add-column and type-promotion reads.
Brief change log
Tests
cargo fmt: passedgit diff --check: passedcargo test -p paimon-integration-tests --test read_tables --no-run: passedAPI and Format
No API or storage format changes. This PR only adds Spark provisioning and Rust integration test coverage.
Documentation
No documentation update required.