[SPARK-44356][SQL] Resolve WITH on top of INSERT INTO via CTEDef
#41922
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
MaxGekk
changed the title
WITH ... INSERT INTOWITH ... INSERT INTO
MaxGekk
changed the title
WITH ... INSERT INTOWITH on top of INSERT INTO via CTEDef
MaxGekk
changed the title
WITH on top of INSERT INTO via CTEDefWITH on top of INSERT INTO via CTEDef
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
In the PR, I propose to resolve
WITHon top ofINSERT INTOvia the regular code path similar to non-commands. In this way,InsertIntoStatementis excluded from commands in the ruleCTESubstitution, andUnresolvedWithis moved intoInsertIntoStatementon top of itsquery.Why are the changes needed?
To improve code maintenance. Right now the CTE resolution code path is diverged: query with commands go into CTE inline code path where non-command queries go into CTEDef code path.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
By running new test: