[SPARK-50600][Connect][SQL] Send optimized plan during ReadyForExecution event #49236
+47
−18
Conversation
This file contains 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
jdesjean
force-pushed
the
SPARK-50600
branch
from
280ec2a to
5e9ad4e
Compare
jdesjean
changed the title
jdesjean
force-pushed
the
SPARK-50600
branch
from
5e9ad4e to
4354ed4
Compare
jdesjean
changed the title
jdesjean
changed the title
jdesjean
force-pushed
the
SPARK-50600
branch
from
4354ed4 to
8173f35
Compare
jdesjean
force-pushed
the
SPARK-50600
branch
from
8173f35 to
b79108f
Compare
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?
As part of SPARK-44145, a callback was added to track completion of analysis and optimization phase of a query. While the analyzed plan is sent during analyzed event the same is not true for the ReadyForExecution event.
This PR adds optimized plan during the ReadyForExecution event.
Why are the changes needed?
The analyzed plan can be use the track the statement type of the query being executed (insert, delete, select). Under certain conditions, the type can change between analysis and optimization. Adding the optimized plan result in more accurate statement type.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit
Was this patch authored or co-authored using generative AI tooling?
No