[SPARK-50612][SQL][FOLLOWUP] Put normalization of inner project lists under a flag #49285
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
MaxGekk
reviewed
Jan 13, 2025
Member
MaxGekk
left a comment
MaxGekk
left a comment
There was a problem hiding this comment.
@mihailotim-db Could you resolve conflicts in the PR, please.
Contributor
Author
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?
Put the change made in #49230 under a flag so that it can be only turned on for single-pass analyzer. This is done in order to protect the Optimizer, in case Optimizer expects certain ordering in the inner project lists.
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?
Modified existing tests.
Was this patch authored or co-authored using generative AI tooling?