[SQL][MINOR] Defensive code for number of Partitions in rCTEs #53270
+2
−1
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
dongjoon-hyun
requested changes
Dec 1, 2025
Member
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Do you think you can add a test case to protect your contribution from any future regression, @Pajaraja ?
Contributor
|
Is it possible to add a unit test by building physical plans directly? e.g. |
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?
Set the number of partitions in recursive CTEs to be at least 1.
Why are the changes needed?
Defensive programming to avoid zero-partition RDDs, which could cause potential issues in downstream operations like coalesce.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing CIs.
Was this patch authored or co-authored using generative AI tooling?
No.