[SPARK-51228][SQL] Introduce subquery normalization to NormalizePlan#49970
Closed
vladimirg-db wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-51228][SQL] Introduce subquery normalization to NormalizePlan#49970vladimirg-db wants to merge 1 commit intoapache:masterfrom
vladimirg-db wants to merge 1 commit intoapache:masterfrom
Conversation
vladimirg-db
force-pushed
the
vladimirg-db/normalize-subqueries-as-well
branch
from
17eee73 to
e7b7a1c
Compare
cloud-fan
approved these changes
Feb 17, 2025
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?
Introduce subquery normalization to NormalizePlan.
Also, perform bottom-up normalization for plans - predicate children have to be normalized first, because they are reordered by
hashCode()value.Why are the changes needed?
This is important for single-pass Analyzer to correctly compare plans with In/Exists/Scalar subqueries.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing tests.
Was this patch authored or co-authored using generative AI tooling?
No.