[SPARK-54668] [SQL] [TEST-ONLY] Add tests for CTEs in multi-children operators #53442
+933
−0
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
dtenedor
approved these changes
Dec 11, 2025
Contributor
dtenedor
left a comment
dtenedor
left a comment
There was a problem hiding this comment.
Thanks for the extra testing!
Contributor
|
It looks like the "Run / Build modules: sql - extended tests" CI job is still running, let's wait for it to finish. |
Contributor
Author
|
@dtenedor it passed! |
Contributor
|
Thanks for working on this, merging to master. |
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?
We miss some golden files for CTEs in multi-children operators. In this issue I propose to add it.
Why are the changes needed?
To improve the coverage for the explained case.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Testing change.
Was this patch authored or co-authored using generative AI tooling?
No.