[SPARK-54975][SQL][TESTS][FOLLOW-UP] Split MergeIntoSchemaEvolutionTests#54391
Closed
szehon-ho wants to merge 2 commits intoapache:masterfrom
Closed
[SPARK-54975][SQL][TESTS][FOLLOW-UP] Split MergeIntoSchemaEvolutionTests#54391szehon-ho wants to merge 2 commits intoapache:masterfrom
szehon-ho wants to merge 2 commits intoapache:masterfrom
Conversation
szehon-ho
force-pushed
the
split_merge_tests
branch
from
83cfd31 to
83f541c
Compare
gengliangwang
approved these changes
Feb 23, 2026
Member
|
Thanks, merging to master |
Member
Author
|
Thanks! |
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
2 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.
What changes were proposed in this pull request?
Split the MergeIntoSchemaEvolutionTests into subtraits
Why are the changes needed?
Test coverage tools instrument these test file, by adding probes into method. This will blow up the compiled bytecode beyond 64k. We found this while trying to instrument these newly added test files.
Does this PR introduce any user-facing change?
No, test only
How was this patch tested?
Run existing test
Was this patch authored or co-authored using generative AI tooling?
Cursor, claude 4.5 opus