You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "junzhang (JIRA)" <ji...@apache.org> on 2018/01/15 07:05:00 UTC
[jira] [Commented] (SPARK-23075) thrift server can not auto cancel
the sql execution if the client is closed
[ https://issues.apache.org/jira/browse/SPARK-23075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325935#comment-16325935 ]
junzhang commented on SPARK-23075:
----------------------------------
already a fix locally. And I will provide the patch for this issue.
> thrift server can not auto cancel the sql execution if the client is closed
> ---------------------------------------------------------------------------
>
> Key: SPARK-23075
> URL: https://issues.apache.org/jira/browse/SPARK-23075
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.2.1
> Reporter: junzhang
> Priority: Major
>
> we use the beeline to connect the spark thrift server to execute sql. when we close the client beeline, the sql submitted by the closed beeline is still running on the server side. The better behavior is that the sql execution on thrift server side should be cancelled.
> The reason is that when the beeline is closed, the corresponding close function is executed on server side and the InterruptedException is triggered. But the exception is ignored. We should catch the exception and cancel the sql execution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org