[spark] Fix merge into update columns detection#7868
Merged
JingsongLi merged 5 commits intoMay 18, 2026
Merged
Conversation
d17a057 to
081fe31
Compare
081fe31 to
2214b94
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.
What changed
This updates Spark merge-into data evolution update column detection so target self-assignments are not treated as modified columns when Spark adds or changes qualifiers. The logic now treats matching AttributeReference exprIds as the same target column, while still including source-side assignments such as target_col = source_col.
Why
Spark AttributeReference.equals also compares qualifiers, so the same target field can compare unequal as file_name#2 versus t.file_name#2. That made updateColumns include unchanged fields and caused partial updates to rewrite more columns than expected.
Validation