[
https://issues.apache.org/jira/browse/KYLIN-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangyuan Feng updated KYLIN-5546:
----------------------------------
Description:
Currently, Kylin has no open APIs to cancel/kill the asynchronous running
query, users have to dig into the log and find out the Spark process, then to
kill the process manually.
Without the entrypoint to kill the running asynchronous queries, the server
will lose control of resources, finally enter into a unstable state.
So I think it's great for Kylin to supply such an open API, to cancel/kill the
asynchronous submitted queries.
was:
Currently, Kylin has no open APIs to cancel/kill a running query, users have to
dig into the log and find out the Spark process, then to kill the process
manually.
So I think it's good for Kylin to supply such an open API.
> Support to cancel asynchronous query job based on the asynchronous query id
> ---------------------------------------------------------------------------
>
> Key: KYLIN-5546
> URL: https://issues.apache.org/jira/browse/KYLIN-5546
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 5.0-alpha
> Reporter: Guangyuan Feng
> Assignee: Guangyuan Feng
> Priority: Major
> Fix For: 5.0-alpha
>
>
> Currently, Kylin has no open APIs to cancel/kill the asynchronous running
> query, users have to dig into the log and find out the Spark process, then to
> kill the process manually.
> Without the entrypoint to kill the running asynchronous queries, the server
> will lose control of resources, finally enter into a unstable state.
> So I think it's great for Kylin to supply such an open API, to cancel/kill
> the asynchronous submitted queries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
