[
https://issues.apache.org/jira/browse/IMPALA-12648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892420#comment-17892420
]
Xuebin Su commented on IMPALA-12648:
------------------------------------
Hi! Regarding the syntax of the command, to support killing one single query,
how about
{code:sql}
KILL QUERY '123:456'
{code}
where 123:456 is the query id of the query we want to kill?
IMHO, this seems more intuitive than using a WHERE clause. We can add new
syntax to support killing multiple queries with one command later.
What do you think? Thanks!
> Support killing queries and sessions programatically
> ----------------------------------------------------
>
> Key: IMPALA-12648
> URL: https://issues.apache.org/jira/browse/IMPALA-12648
> Project: IMPALA
> Issue Type: New Feature
> Components: Frontend
> Affects Versions: Impala 4.3.0
> Reporter: Manish Maheshwari
> Assignee: Xuebin Su
> Priority: Major
> Attachments: ranger_policy_hiveservice_7.3.0.0-128_screenshot.png
>
>
> Support killing queries and sessions programatically via kill commands to be
> able to manage impala running workloads.
> 1. Killing Queries that are currently running
> {code:java}
> -- Forcibly terminates query with the specified query_id:
> KILL QUERY WHERE query_id='634bf9fcf55278eb:ac0ef05300000000' {code}
> For queries that are the finished and waiting to be closed, this command
> should close them
> 2. Killing sessions that are open
> {code:java}
> -- Forcibly terminates session and closes all queries:
> KILL SESSION WHERE session_id='2644d52c79c4c1e4:e974538f2189ed82' {code}
> this command should terminate the session and kill all active queries and
> close all queries that are finished and are waiting to be closed.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
