[jira] [Commented] (KYLIN-5546) Support to cancel asynchronous query job based on the asynchronous query id
[
https://issues.apache.org/jira/browse/KYLIN-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729598#comment-17729598
]
ASF GitHub Bot commented on KYLIN-5546:
---
fengguangyuan opened a new pull request, #2121:
URL: https://github.com/apache/kylin/pull/2121
## Proposed changes
As described in JIRA
[KYLIN-5546](https://issues.apache.org/jira/browse/KYLIN-5546)，this PR supply a
DELETE REST API `/async_query/stop/{query_id:.+}` to kill the submitted
asynchronous query by the `query id`.
## Branch to commit
- [ ] Branch **kylin3** for v2.x to v3.x
- [ ] Branch **kylin4** for v4.x
- [ ] Branch **kylin5** for v5.x
## Types of changes
What types of changes does your code introduce to Kylin?
_Put an `x` in the boxes that apply_
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation Update (if none of the other choices apply)
## Checklist
_Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look for
before merging your code._
- [ ] I have created an issue on [Kylin's
jira](https://issues.apache.org/jira/browse/KYLIN), and have described the
bug/feature there in detail
- [ ] Commit messages in my PR start with the related jira ID, like
"KYLIN- Make Kylin project open-source"
- [ ] Compiling and unit tests pass locally with my changes
- [ ] I have added tests that prove my fix is effective or that my feature
works
- [ ] I have added necessary documentation (if appropriate)
- [ ] Any dependent changes have been merged
## Further comments
If this is a relatively large or complex change, kick off the discussion at
u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the
solution you did and what alternatives you considered, etc...
> 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)
[GitHub] [kylin] fengguangyuan opened a new pull request, #2121: KYLIN-5546 Add stop async query job api.
fengguangyuan opened a new pull request, #2121:
URL: https://github.com/apache/kylin/pull/2121
## Proposed changes
As described in JIRA
[KYLIN-5546](https://issues.apache.org/jira/browse/KYLIN-5546)，this PR supply a
DELETE REST API `/async_query/stop/{query_id:.+}` to kill the submitted
asynchronous query by the `query id`.
## Branch to commit
- [ ] Branch **kylin3** for v2.x to v3.x
- [ ] Branch **kylin4** for v4.x
- [ ] Branch **kylin5** for v5.x
## Types of changes
What types of changes does your code introduce to Kylin?
_Put an `x` in the boxes that apply_
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation Update (if none of the other choices apply)
## Checklist
_Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look for
before merging your code._
- [ ] I have created an issue on [Kylin's
jira](https://issues.apache.org/jira/browse/KYLIN), and have described the
bug/feature there in detail
- [ ] Commit messages in my PR start with the related jira ID, like
"KYLIN- Make Kylin project open-source"
- [ ] Compiling and unit tests pass locally with my changes
- [ ] I have added tests that prove my fix is effective or that my feature
works
- [ ] I have added necessary documentation (if appropriate)
- [ ] Any dependent changes have been merged
## Further comments
If this is a relatively large or complex change, kick off the discussion at
u...@kylin.apache.org or d...@kylin.apache.org by explaining why you chose the
solution you did and what alternatives you considered, etc...
--
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.
To unsubscribe, e-mail: issues-unsubscr...@kylin.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (KYLIN-5546) Support to cancel asynchronous query job based on the asynchronous query id
[ 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)
[jira] [Assigned] (KYLIN-5547) change the style of recognize aggregate modal
[ https://issues.apache.org/jira/browse/KYLIN-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Xia reassigned KYLIN-5547: Assignee: Laura Xia > change the style of recognize aggregate modal > -- > > Key: KYLIN-5547 > URL: https://issues.apache.org/jira/browse/KYLIN-5547 > Project: Kylin > Issue Type: Improvement >Reporter: Laura Xia >Assignee: Laura Xia >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5547) change the style of recognize aggregate modal
[ https://issues.apache.org/jira/browse/KYLIN-5547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Xia updated KYLIN-5547: - Fix Version/s: 5.0-beta > change the style of recognize aggregate modal > -- > > Key: KYLIN-5547 > URL: https://issues.apache.org/jira/browse/KYLIN-5547 > Project: Kylin > Issue Type: Improvement >Reporter: Laura Xia >Assignee: Laura Xia >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5547) change the style of recognize aggregate modal
Laura Xia created KYLIN-5547: Summary: change the style of recognize aggregate modal Key: KYLIN-5547 URL: https://issues.apache.org/jira/browse/KYLIN-5547 Project: Kylin Issue Type: Improvement Reporter: Laura Xia -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (KYLIN-5546) Support to cancel asynchronous query job based on the asynchronous query id
[ https://issues.apache.org/jira/browse/KYLIN-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guangyuan Feng reassigned KYLIN-5546: - Assignee: Guangyuan Feng > 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 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5546) Support to cancel asynchronous query job based on the asynchronous query id
Guangyuan Feng created KYLIN-5546: - Summary: 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 Fix For: 5.0-alpha 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5545) Try best to interrupt running queries and limit the number of queries to run
Guangyuan Feng created KYLIN-5545: - Summary: Try best to interrupt running queries and limit the number of queries to run Key: KYLIN-5545 URL: https://issues.apache.org/jira/browse/KYLIN-5545 Project: Kylin Issue Type: Bug Components: Query Engine Affects Versions: 5.0-alpha Reporter: Guangyuan Feng Fix For: 5.0-alpha There are two issues will decrease the stability of Kylin: # Don't try best to cancel the running queries if occurred interruptions, leading to the useless consumptions of calculating resources. # Don't limit the number of queries that can be pushed down, leading to too many queries to run, evenly to a OOM. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5544) Provides Spark DDL & DML execution capability in GUI
[ https://issues.apache.org/jira/browse/KYLIN-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Xia updated KYLIN-5544: - Fix Version/s: 5.0-beta > Provides Spark DDL & DML execution capability in GUI > > > Key: KYLIN-5544 > URL: https://issues.apache.org/jira/browse/KYLIN-5544 > Project: Kylin > Issue Type: New Feature >Reporter: Laura Xia >Assignee: Laura Xia >Priority: Major > Fix For: 5.0-beta > > > h2. Why 和 背景 > * 有在 Kylin 中自定义视图的需求。其解决的核心痛点是，数仓部为了数据安全通常是一刀切，封闭分析师直接对 Hive > 操作数据的所有权限。然而，分析师/建模师常常需要在最后一公里对数据做一些调整，因此从权限角度，希望 Kylin > 侧可以提供创建视图的能力，达到向分析师/建模师赋能的效果。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (KYLIN-5544) Provides Spark DDL & DML execution capability in GUI
[ https://issues.apache.org/jira/browse/KYLIN-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Xia reassigned KYLIN-5544: Assignee: Laura Xia > Provides Spark DDL & DML execution capability in GUI > > > Key: KYLIN-5544 > URL: https://issues.apache.org/jira/browse/KYLIN-5544 > Project: Kylin > Issue Type: New Feature >Reporter: Laura Xia >Assignee: Laura Xia >Priority: Major > > h2. Why 和 背景 > * 有在 Kylin 中自定义视图的需求。其解决的核心痛点是，数仓部为了数据安全通常是一刀切，封闭分析师直接对 Hive > 操作数据的所有权限。然而，分析师/建模师常常需要在最后一公里对数据做一些调整，因此从权限角度，希望 Kylin > 侧可以提供创建视图的能力，达到向分析师/建模师赋能的效果。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5544) Provides Spark DDL & DML execution capability in GUI
Laura Xia created KYLIN-5544: Summary: Provides Spark DDL & DML execution capability in GUI Key: KYLIN-5544 URL: https://issues.apache.org/jira/browse/KYLIN-5544 Project: Kylin Issue Type: New Feature Reporter: Laura Xia h2. Why 和 背景 * 有在 Kylin 中自定义视图的需求。其解决的核心痛点是，数仓部为了数据安全通常是一刀切，封闭分析师直接对 Hive 操作数据的所有权限。然而，分析师/建模师常常需要在最后一公里对数据做一些调整，因此从权限角度，希望 Kylin 侧可以提供创建视图的能力，达到向分析师/建模师赋能的效果。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KYLIN-5543) Recognize Aggregate demension validate bug
[ https://issues.apache.org/jira/browse/KYLIN-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Xia updated KYLIN-5543: - Fix Version/s: 5.0-beta > Recognize Aggregate demension validate bug > -- > > Key: KYLIN-5543 > URL: https://issues.apache.org/jira/browse/KYLIN-5543 > Project: Kylin > Issue Type: Bug >Reporter: Laura Xia >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (KYLIN-5543) Recognize Aggregate demension validate bug
[ https://issues.apache.org/jira/browse/KYLIN-5543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Xia reassigned KYLIN-5543: Assignee: Laura Xia > Recognize Aggregate demension validate bug > -- > > Key: KYLIN-5543 > URL: https://issues.apache.org/jira/browse/KYLIN-5543 > Project: Kylin > Issue Type: Bug >Reporter: Laura Xia >Assignee: Laura Xia >Priority: Major > Fix For: 5.0-beta > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (KYLIN-5543) Recognize Aggregate demension validate bug
Laura Xia created KYLIN-5543: Summary: Recognize Aggregate demension validate bug Key: KYLIN-5543 URL: https://issues.apache.org/jira/browse/KYLIN-5543 Project: Kylin Issue Type: Bug Reporter: Laura Xia -- This message was sent by Atlassian Jira (v8.20.10#820010)
