You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Su Ralph (JIRA)" <ji...@apache.org> on 2016/02/03 04:27:39 UTC
[jira] [Updated] (KYLIN-1398) Query explanation
[ https://issues.apache.org/jira/browse/KYLIN-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Su Ralph updated KYLIN-1398:
----------------------------
Description:
When troubleshooting kylin query, we could use "Insight" tab to issue query, then checking the kylin.log. This definitely the right way, but make it only available to kylin admin who can access the kylin log.
Since most query system provide query explanation(same as calcite), Kylin might also output query explanation in response. Say when issue query with explain=true , the query response would return structured explanation, like how many htable touched, how many records read from each htable and the time consumption.
Both kylin owner and user should benefit from such feature.
was:
When troubleshooting kylin query, we could user "Insight" tab to issue query, then checking the kylin.log. This definitely the right way, but make it only available to kylin admin who can access the kylin log.
Since most query system provide query explanation(same as calcite), Kylin might also output query explanation in response. Say when issue query with explain=true , the query response would return structured explanation, like how many htable touched, how many records read from each htable and the time consumption.
Both kylin owner and user should benefit from such feature.
> Query explanation
> ------------------
>
> Key: KYLIN-1398
> URL: https://issues.apache.org/jira/browse/KYLIN-1398
> Project: Kylin
> Issue Type: Improvement
> Components: Query Engine
> Reporter: Su Ralph
> Assignee: liyang
> Fix For: 2.0
>
>
> When troubleshooting kylin query, we could use "Insight" tab to issue query, then checking the kylin.log. This definitely the right way, but make it only available to kylin admin who can access the kylin log.
> Since most query system provide query explanation(same as calcite), Kylin might also output query explanation in response. Say when issue query with explain=true , the query response would return structured explanation, like how many htable touched, how many records read from each htable and the time consumption.
> Both kylin owner and user should benefit from such feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)