You are viewing a plain text version of this content. The canonical link for it is here.

Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2021/01/13 02:51:29 UTC

[GitHub] [spark] yaooqinn commented on pull request #31119: [SPARK-34064][SQL] Cancel the running broadcast sub-jobs when SQL statement is cancelled

yaooqinn commented on pull request #31119:
URL: https://github.com/apache/spark/pull/31119#issuecomment-759169196


   Nice catch. 
   
   >  BTW why doesn't STS use SQL execution ID to cancel the jobs for a SQL query?
   
   I have no idea. I guess the IDs are mainly used for the listeners (SQLAppStatusListener and HiveThriftServer2Listener) to capture and track different SQL states. 
   
   For canceling related jobs, I think the IDs  are both OK to use I we want them to be unified
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org