[SPARK-55811] [SQL] Catch NonFatal instead of UnresolvedException when calling nodeWithOutputColumnsString#54600
Closed
mihailoale-db wants to merge 1 commit intoapache:masterfrom
Closed
Conversation
mihailoale-db
force-pushed
the
fixunioninfoissue
branch
from
696a845 to
7566881
Compare
Contributor
Author
|
@cloud-fan PTAL when you find time. Thanks! |
cloud-fan
approved these changes
Mar 4, 2026
Contributor
|
thanks, merging to master! |
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?
fails with
CANNOT_MERGE_INCOMPATIBLE_DATA_TYPEwhenspark.sql.planChangeLog.levelis set toinfobecause we callUnion.outputtoo early (before type coercion is performed). In this PR I propose to fix it by catchingNonFatalinstead ofUnresolvedExceptionwhen callingnodeWithOutputColumnsString.Why are the changes needed?
To fix an issue.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added + existing tests.
Was this patch authored or co-authored using generative AI tooling?
No.