[
https://issues.apache.org/jira/browse/SPARK-50600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Francois Desjeans Gauthier updated SPARK-50600:
----------------------------------------------------
Description:
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 when
analysis completes successfully it does not when it fail. In that case, we
should fallback to the ParsedPlan.
The purpose of the analyze event is to track when analysis completes, as such
it should also be sent on both success & failure.
was:
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. 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.
This PR adds optimized plan during the ReadyForExecution event.
> Set analyzed on analysis failure
> --------------------------------
>
> Key: SPARK-50600
> URL: https://issues.apache.org/jira/browse/SPARK-50600
> Project: Spark
> Issue Type: Improvement
> Components: Connect, SQL
> Affects Versions: 4.0.0
> Reporter: Jean-Francois Desjeans Gauthier
> Priority: Major
> Labels: pull-request-available
>
> 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 when
> analysis completes successfully it does not when it fail. In that case, we
> should fallback to the ParsedPlan.
> The purpose of the analyze event is to track when analysis completes, as such
> it should also be sent on both success & failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
