[SPARK-56032][SQL][FOLLOW-UP] Fix comments in FilterExec CSE #54975
Closed
LuciferYang wants to merge 2 commits intoapache:masterfrom
Closed
[SPARK-56032][SQL][FOLLOW-UP] Fix comments in FilterExec CSE #54975LuciferYang wants to merge 2 commits intoapache:masterfrom
LuciferYang wants to merge 2 commits intoapache:masterfrom
Conversation
Contributor
Author
|
cc @cloud-fan |
Member
|
Thank you, Jie. I'll leave this to Wenchen~ |
cloud-fan
approved these changes
Mar 25, 2026
dongjoon-hyun
approved these changes
Mar 25, 2026
Member
|
Merged to master for Apache Spark 4.2.0. |
Contributor
Author
|
Thanks @dongjoon-hyun and @cloud-fan |
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
3 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?
This PR addresses review comments from cloud-fan in #54862
Why are the changes needed?
To improve code clarity and prevent potential future bugs from incorrect refactoring.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass Github Actions
Was this patch authored or co-authored using generative AI tooling?
No