You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Juliusz Sompolski (Jira)" <ji...@apache.org> on 2019/10/25 14:59:01 UTC

[jira] [Commented] (HIVE-17483) HS2 kill command to kill queries using query id

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

Juliusz Sompolski commented on HIVE-17483:
------------------------------------------

It seems that up until ~2017, the protocol version of Thriftserver was being updated with changes like this, but it seems to not be done anymore - this change has not bumbed the HIVE_CLI_SERVICE_PROTOCOL version when adding the new thrift messages.
What is currently used to ensure protocol compatibility?

> HS2 kill command to kill queries using query id
> -----------------------------------------------
>
>                 Key: HIVE-17483
>                 URL: https://issues.apache.org/jira/browse/HIVE-17483
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Thejas Nair
>            Assignee: Teddy Choi
>            Priority: Major
>              Labels: TODOC3.0
>             Fix For: 3.0.0
>
>         Attachments: HIVE-17483.1.patch, HIVE-17483.10.patch, HIVE-17483.2.patch, HIVE-17483.2.patch, HIVE-17483.3.patch, HIVE-17483.4.patch, HIVE-17483.5.patch, HIVE-17483.6.patch, HIVE-17483.7.patch, HIVE-17483.8.patch, HIVE-17483.9.patch
>
>
> For administrators, it is important to be able to kill queries if required. 
> Currently, there is no clean way to do it.
> It would help to have a "kill query <query id>" command that can be run using odbc/jdbc against a HiveServer2 instance, to kill a query with that queryid running in that instance.
> Authorization will have to be done to ensure that the user that is invoking the API is allowed to perform this action.
> In case of SQL std authorization, this would require admin role.



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