[SPARK-52060][SQL] Make OneRowRelationExec node
#50849
Open
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
richardc-db
changed the title
OneRowRelationExec nodeOneRowRelationExec node
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?
creates a new OneRowRelationExec node, which is more or less a copy of the RDDScanExec node.
We want a dedicated node because this helps make it more clear when a one row relation, i.e. for patterns like
SELECT version()is used.Why are the changes needed?
this makes it more clear in the code that a one row relation is used and allows us to avoid checking the hard coded "OneRowRelation" string when pattern matching.
Does this PR introduce any user-facing change?
yes, the plan will now be
OneRowRelationExecrather thanRDDScanExec. The plan string should be the same, however.How was this patch tested?
added UTs
Was this patch authored or co-authored using generative AI tooling?