[ 
https://issues.apache.org/jira/browse/SPARK-32057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143230#comment-17143230
 ] 

Apache Spark commented on SPARK-32057:
--------------------------------------

User 'alismess-db' has created a pull request for this issue:
https://github.com/apache/spark/pull/28912

> SparkExecuteStatementOperation does not set CANCELED state correctly 
> ---------------------------------------------------------------------
>
>                 Key: SPARK-32057
>                 URL: https://issues.apache.org/jira/browse/SPARK-32057
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Ali Smesseim
>            Priority: Major
>
> https://github.com/apache/spark/pull/28671 introduced changes that changed 
> the way cleanup is done in SparkExecuteStatementOperation. In cancel(), 
> cleanup (killing jobs) used to be done after setting state to CANCELED. Now, 
> the order is reversed. Jobs are killed first, causing exception to be thrown 
> inside execute(), so the status of the operation becomes ERROR before being 
> set to CANCELED.
> cc [~juliuszsompolski]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to