[SPARK-52686][SQL][FOLLOWUP] Don't push Project through Union if there are duplicates in the project list
#51628
+46
−37
Conversation
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
mihailotim-db
force-pushed
the
mihailotim-db/push_through_project
branch
from
e20fe34 to
bf7cde6
Compare
vladimirg-db
approved these changes
Jul 23, 2025
agubichev
approved these changes
Jul 23, 2025
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 changes were proposed in this pull request?
Don't push
ProjectthroughUnionif there are duplicates in the project list.Why are the changes needed?
This is fixing a change made in #51376. Pushing down the
Projectand deduplicating its output with aliases can causeDUPLICATED_FIELD_NAME_IN_ARROW_STRUCTin FlatMapGroup queries because schema deduplication logic relies onExprIds in order to deduplicate field names.Does this PR introduce any user-facing change?
No
How was this patch tested?
Added a new test case.
Was this patch authored or co-authored using generative AI tooling?
No