juliuszsompolski commented on a change in pull request #30481:
URL: https://github.com/apache/spark/pull/30481#discussion_r539240753



##########
File path: 
sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala
##########
@@ -937,6 +937,14 @@ object SQLConf {
       .timeConf(TimeUnit.SECONDS)
       .createWithDefault(0L)
 
+  val THRIFTSERVER_FORCE_CANCEL =
+    buildConf("spark.sql.thriftServer.interruptOnCancel")
+      .doc("When true, all running tasks will be interrupted if one cancels a 
query. " +
+        "When false, all running tasks will be remained until finished.")
+      .version("3.2.0")
+      .booleanConf
+      .createWithDefault(false)

Review comment:
       I wasn't aware that cancelling a job group leaves currently running 
tasks running to completion.
   Why not set it true? What are the disadvantages?




----------------------------------------------------------------
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:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to