[SPARK-50319] Reorder ResolveIdentifierClause and BindParameter rules#48849
Closed
srielau wants to merge 3 commits intoapache:masterfrom
Closed
[SPARK-50319] Reorder ResolveIdentifierClause and BindParameter rules#48849srielau wants to merge 3 commits intoapache:masterfrom
srielau wants to merge 3 commits intoapache:masterfrom
Conversation
8256d25 to
ead1fc9
Compare
|
We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
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 changes were proposed in this pull request?
The current relative order of rules is:
These rules interact in exactly the opposite way as they are listed:
We propose to move BindParameters and ResolveIdentifierClause up.
Why are the changes needed?
This has two effects:
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests suffice
Was this patch authored or co-authored using generative AI tooling?
No