[SPARK-56450][SQL] Add merge into schema evolution test with source subquery alias#55304
Open
szehon-ho wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-56450][SQL] Add merge into schema evolution test with source subquery alias#55304szehon-ho wants to merge 1 commit intoapache:masterfrom
szehon-ho wants to merge 1 commit intoapache:masterfrom
Conversation
szehon-ho
force-pushed
the
merge-into-schema-evolution-source-alias
branch
from
6558005 to
b4a702b
Compare
Member
Author
|
This was from an offline conversation. I see its asked here as well, we can add it in that pr, this is just a demonstration that this test behaves as expected #55239 (comment) |
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
1 participant
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.
What changes were proposed in this pull request?
Add tests for MERGE INTO schema evolution when the source is a subquery with projection and alias (e.g.,
USING (SELECT ...) AS s), covering INSERT * with and without schema evolution.Why are the changes needed?
This source pattern was not covered by existing schema evolution tests.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
New tests in
MergeIntoSchemaEvolutionExtraSQLTests, run viaDeltaBasedMergeIntoSchemaEvolutionSQLSuite.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Cursor (Claude)