[jira] [Commented] (KYLIN-3119) A few bugs in the function 'massageSql' of 'QueryUtil.java'
[
https://issues.apache.org/jira/browse/KYLIN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379643#comment-16379643
]
Roger Shi commented on KYLIN-3119:
--
Thank you [~peng.jianhua], I have some comments in the PR. Would you please
have a check?
> A few bugs in the function 'massageSql' of 'QueryUtil.java'
> ---
>
> Key: KYLIN-3119
> URL: https://issues.apache.org/jira/browse/KYLIN-3119
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments:
> 0001-KYLIN-3119-A-few-bugs-in-the-function-massageSql-of-.patch,
> 0001-KYLIN-3119-add-test-cases.patch,
> 0001-kylin-3119-add-more-test-cases-with-enter-and-space.patch,
> 0001-kylin-3119.patch, 01.PNG, 02.PNG
>
>
> in the function 'massageSql' of 'QueryUtil.java',there are a few bugs:
> 01:
> {code:java}
> while (sql.endsWith(";"))
> sql = sql.substring(0, sql.length() - 1);
> {code}
> if the sql end with ';' and after the ';' still has comments,will be
> error.Because the sql will add ("\nLIMIT " + limit) at the end.
> 02:
> {code:java}
> if (limit > 0 && !sql.toLowerCase().contains("limit")) {
> sql += ("\nLIMIT " + limit);
> }
> if (offset > 0 && !sql.toLowerCase().contains("offset")) {
> sql += ("\nOFFSET " + offset);
> }
> {code}
> if the sql already has word 'limit' in it,such as Alias,Subquery,Comments,the
> ‘limit’ in the Input box will be invalid.
> for example,the sql has subquery,and there is 'limit' in subquery.
> {code:java}
> select KYLIN_SALES.PART_DT, count(KYLIN_SALES.PRICE)
> from KYLIN_SALES
> inner join (select ACCOUNT_ID, ACCOUNT_BUYER_LEVEL from KYLIN_ACCOUNT where
> ACCOUNT_COUNTRY = 'US' limit 1) as TT
> on KYLIN_SALES.BUYER_ID = TT.ACCOUNT_ID
> group by KYLIN_SALES.PART_DT
> {code}
> the ‘limit’ in the Input box will be invalid.please refer to 01.png and
> 02.png.
> 03:
> {code:java}
> // https://issues.apache.org/jira/browse/KYLIN-2649
> if (kylinConfig.getForceLimit() > 0 &&
> !sql.toLowerCase().contains("limit")
> && sql.toLowerCase().contains("*")) {
> sql += ("\nLIMIT " + kylinConfig.getForceLimit());
> }
> {code}
> Because KYLIN-2649 is still unresolved,so I didn't change the code,but it
> has same 'limit' word bugs like above.
> And there are some situations that the sql contains \*,such as
> {code:java}count(*),kylin_sales.*{code}
> Maybe the \* in subquery too.
> it seems improperly to deal with the sql just use {code:java}
> sql.toLowerCase().contains("*")
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3119) A few bugs in the function 'massageSql' of 'QueryUtil.java'
[
https://issues.apache.org/jira/browse/KYLIN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377959#comment-16377959
]
Roger Shi commented on KYLIN-3119:
--
[~peng.jianhua], it's a commit, not a PR. On how to create a PR, please refer
to https://help.github.com/articles/about-pull-requests/
> A few bugs in the function 'massageSql' of 'QueryUtil.java'
> ---
>
> Key: KYLIN-3119
> URL: https://issues.apache.org/jira/browse/KYLIN-3119
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments:
> 0001-KYLIN-3119-A-few-bugs-in-the-function-massageSql-of-.patch,
> 0001-KYLIN-3119-add-test-cases.patch,
> 0001-kylin-3119-add-more-test-cases-with-enter-and-space.patch,
> 0001-kylin-3119.patch, 01.PNG, 02.PNG
>
>
> in the function 'massageSql' of 'QueryUtil.java',there are a few bugs:
> 01:
> {code:java}
> while (sql.endsWith(";"))
> sql = sql.substring(0, sql.length() - 1);
> {code}
> if the sql end with ';' and after the ';' still has comments,will be
> error.Because the sql will add ("\nLIMIT " + limit) at the end.
> 02:
> {code:java}
> if (limit > 0 && !sql.toLowerCase().contains("limit")) {
> sql += ("\nLIMIT " + limit);
> }
> if (offset > 0 && !sql.toLowerCase().contains("offset")) {
> sql += ("\nOFFSET " + offset);
> }
> {code}
> if the sql already has word 'limit' in it,such as Alias,Subquery,Comments,the
> ‘limit’ in the Input box will be invalid.
> for example,the sql has subquery,and there is 'limit' in subquery.
> {code:java}
> select KYLIN_SALES.PART_DT, count(KYLIN_SALES.PRICE)
> from KYLIN_SALES
> inner join (select ACCOUNT_ID, ACCOUNT_BUYER_LEVEL from KYLIN_ACCOUNT where
> ACCOUNT_COUNTRY = 'US' limit 1) as TT
> on KYLIN_SALES.BUYER_ID = TT.ACCOUNT_ID
> group by KYLIN_SALES.PART_DT
> {code}
> the ‘limit’ in the Input box will be invalid.please refer to 01.png and
> 02.png.
> 03:
> {code:java}
> // https://issues.apache.org/jira/browse/KYLIN-2649
> if (kylinConfig.getForceLimit() > 0 &&
> !sql.toLowerCase().contains("limit")
> && sql.toLowerCase().contains("*")) {
> sql += ("\nLIMIT " + kylinConfig.getForceLimit());
> }
> {code}
> Because KYLIN-2649 is still unresolved,so I didn't change the code,but it
> has same 'limit' word bugs like above.
> And there are some situations that the sql contains \*,such as
> {code:java}count(*),kylin_sales.*{code}
> Maybe the \* in subquery too.
> it seems improperly to deal with the sql just use {code:java}
> sql.toLowerCase().contains("*")
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3119) A few bugs in the function 'massageSql' of 'QueryUtil.java'
[
https://issues.apache.org/jira/browse/KYLIN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376437#comment-16376437
]
Roger Shi commented on KYLIN-3119:
--
[~peng.jianhua] Sorry for the late response. As gitbox is online now, do you
mind sending a github PR? It's supposed to be easier to communicate on code.
> A few bugs in the function 'massageSql' of 'QueryUtil.java'
> ---
>
> Key: KYLIN-3119
> URL: https://issues.apache.org/jira/browse/KYLIN-3119
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments:
> 0001-KYLIN-3119-A-few-bugs-in-the-function-massageSql-of-.patch,
> 0001-KYLIN-3119-add-test-cases.patch,
> 0001-kylin-3119-add-more-test-cases-with-enter-and-space.patch,
> 0001-kylin-3119.patch, 01.PNG, 02.PNG
>
>
> in the function 'massageSql' of 'QueryUtil.java',there are a few bugs:
> 01:
> {code:java}
> while (sql.endsWith(";"))
> sql = sql.substring(0, sql.length() - 1);
> {code}
> if the sql end with ';' and after the ';' still has comments,will be
> error.Because the sql will add ("\nLIMIT " + limit) at the end.
> 02:
> {code:java}
> if (limit > 0 && !sql.toLowerCase().contains("limit")) {
> sql += ("\nLIMIT " + limit);
> }
> if (offset > 0 && !sql.toLowerCase().contains("offset")) {
> sql += ("\nOFFSET " + offset);
> }
> {code}
> if the sql already has word 'limit' in it,such as Alias,Subquery,Comments,the
> ‘limit’ in the Input box will be invalid.
> for example,the sql has subquery,and there is 'limit' in subquery.
> {code:java}
> select KYLIN_SALES.PART_DT, count(KYLIN_SALES.PRICE)
> from KYLIN_SALES
> inner join (select ACCOUNT_ID, ACCOUNT_BUYER_LEVEL from KYLIN_ACCOUNT where
> ACCOUNT_COUNTRY = 'US' limit 1) as TT
> on KYLIN_SALES.BUYER_ID = TT.ACCOUNT_ID
> group by KYLIN_SALES.PART_DT
> {code}
> the ‘limit’ in the Input box will be invalid.please refer to 01.png and
> 02.png.
> 03:
> {code:java}
> // https://issues.apache.org/jira/browse/KYLIN-2649
> if (kylinConfig.getForceLimit() > 0 &&
> !sql.toLowerCase().contains("limit")
> && sql.toLowerCase().contains("*")) {
> sql += ("\nLIMIT " + kylinConfig.getForceLimit());
> }
> {code}
> Because KYLIN-2649 is still unresolved,so I didn't change the code,but it
> has same 'limit' word bugs like above.
> And there are some situations that the sql contains \*,such as
> {code:java}count(*),kylin_sales.*{code}
> Maybe the \* in subquery too.
> it seems improperly to deal with the sql just use {code:java}
> sql.toLowerCase().contains("*")
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3119) A few bugs in the function 'massageSql' of 'QueryUtil.java'
[
https://issues.apache.org/jira/browse/KYLIN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357945#comment-16357945
]
Roger Shi edited comment on KYLIN-3119 at 2/9/18 5:40 AM:
--
[~peng.jianhua], for this line I also have a question. If a string contains
continous white space such as 'A B', it will be replaced to 'A B'. It's
not the expected behavior. It seems more tests are required to cover these
cases.
was (Author: r0ger):
[~peng.jianhua], for this line I also have a question. If a string contains
continous white space such as 'A B', it will be replaced to 'A B'. It's
not the expected behavior.
> A few bugs in the function 'massageSql' of 'QueryUtil.java'
> ---
>
> Key: KYLIN-3119
> URL: https://issues.apache.org/jira/browse/KYLIN-3119
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments:
> 0001-KYLIN-3119-A-few-bugs-in-the-function-massageSql-of-.patch,
> 0001-KYLIN-3119-add-test-cases.patch, 01.PNG, 02.PNG
>
>
> in the function 'massageSql' of 'QueryUtil.java',there are a few bugs:
> 01:
> {code:java}
> while (sql.endsWith(";"))
> sql = sql.substring(0, sql.length() - 1);
> {code}
> if the sql end with ';' and after the ';' still has comments,will be
> error.Because the sql will add ("\nLIMIT " + limit) at the end.
> 02:
> {code:java}
> if (limit > 0 && !sql.toLowerCase().contains("limit")) {
> sql += ("\nLIMIT " + limit);
> }
> if (offset > 0 && !sql.toLowerCase().contains("offset")) {
> sql += ("\nOFFSET " + offset);
> }
> {code}
> if the sql already has word 'limit' in it,such as Alias,Subquery,Comments,the
> ‘limit’ in the Input box will be invalid.
> for example,the sql has subquery,and there is 'limit' in subquery.
> {code:java}
> select KYLIN_SALES.PART_DT, count(KYLIN_SALES.PRICE)
> from KYLIN_SALES
> inner join (select ACCOUNT_ID, ACCOUNT_BUYER_LEVEL from KYLIN_ACCOUNT where
> ACCOUNT_COUNTRY = 'US' limit 1) as TT
> on KYLIN_SALES.BUYER_ID = TT.ACCOUNT_ID
> group by KYLIN_SALES.PART_DT
> {code}
> the ‘limit’ in the Input box will be invalid.please refer to 01.png and
> 02.png.
> 03:
> {code:java}
> // https://issues.apache.org/jira/browse/KYLIN-2649
> if (kylinConfig.getForceLimit() > 0 &&
> !sql.toLowerCase().contains("limit")
> && sql.toLowerCase().contains("*")) {
> sql += ("\nLIMIT " + kylinConfig.getForceLimit());
> }
> {code}
> Because KYLIN-2649 is still unresolved,so I didn't change the code,but it
> has same 'limit' word bugs like above.
> And there are some situations that the sql contains \*,such as
> {code:java}count(*),kylin_sales.*{code}
> Maybe the \* in subquery too.
> it seems improperly to deal with the sql just use {code:java}
> sql.toLowerCase().contains("*")
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3119) A few bugs in the function 'massageSql' of 'QueryUtil.java'
[
https://issues.apache.org/jira/browse/KYLIN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357945#comment-16357945
]
Roger Shi commented on KYLIN-3119:
--
[~peng.jianhua], for this line I also have a question. If a string contains
continous white space such as 'A B', it will be replaced to 'A B'. It's
not the expected behavior.
> A few bugs in the function 'massageSql' of 'QueryUtil.java'
> ---
>
> Key: KYLIN-3119
> URL: https://issues.apache.org/jira/browse/KYLIN-3119
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments:
> 0001-KYLIN-3119-A-few-bugs-in-the-function-massageSql-of-.patch,
> 0001-KYLIN-3119-add-test-cases.patch, 01.PNG, 02.PNG
>
>
> in the function 'massageSql' of 'QueryUtil.java',there are a few bugs:
> 01:
> {code:java}
> while (sql.endsWith(";"))
> sql = sql.substring(0, sql.length() - 1);
> {code}
> if the sql end with ';' and after the ';' still has comments,will be
> error.Because the sql will add ("\nLIMIT " + limit) at the end.
> 02:
> {code:java}
> if (limit > 0 && !sql.toLowerCase().contains("limit")) {
> sql += ("\nLIMIT " + limit);
> }
> if (offset > 0 && !sql.toLowerCase().contains("offset")) {
> sql += ("\nOFFSET " + offset);
> }
> {code}
> if the sql already has word 'limit' in it,such as Alias,Subquery,Comments,the
> ‘limit’ in the Input box will be invalid.
> for example,the sql has subquery,and there is 'limit' in subquery.
> {code:java}
> select KYLIN_SALES.PART_DT, count(KYLIN_SALES.PRICE)
> from KYLIN_SALES
> inner join (select ACCOUNT_ID, ACCOUNT_BUYER_LEVEL from KYLIN_ACCOUNT where
> ACCOUNT_COUNTRY = 'US' limit 1) as TT
> on KYLIN_SALES.BUYER_ID = TT.ACCOUNT_ID
> group by KYLIN_SALES.PART_DT
> {code}
> the ‘limit’ in the Input box will be invalid.please refer to 01.png and
> 02.png.
> 03:
> {code:java}
> // https://issues.apache.org/jira/browse/KYLIN-2649
> if (kylinConfig.getForceLimit() > 0 &&
> !sql.toLowerCase().contains("limit")
> && sql.toLowerCase().contains("*")) {
> sql += ("\nLIMIT " + kylinConfig.getForceLimit());
> }
> {code}
> Because KYLIN-2649 is still unresolved,so I didn't change the code,but it
> has same 'limit' word bugs like above.
> And there are some situations that the sql contains \*,such as
> {code:java}count(*),kylin_sales.*{code}
> Maybe the \* in subquery too.
> it seems improperly to deal with the sql just use {code:java}
> sql.toLowerCase().contains("*")
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3119) A few bugs in the function 'massageSql' of 'QueryUtil.java'
[
https://issues.apache.org/jira/browse/KYLIN-3119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357867#comment-16357867
]
Roger Shi commented on KYLIN-3119:
--
Hi [~peng.jianhua], it's a good catch. I have one comment on the patch. The
regex seems not to match multi-line query. Would you please add a UT to prove
it?
> A few bugs in the function 'massageSql' of 'QueryUtil.java'
> ---
>
> Key: KYLIN-3119
> URL: https://issues.apache.org/jira/browse/KYLIN-3119
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Major
> Attachments:
> 0001-KYLIN-3119-A-few-bugs-in-the-function-massageSql-of-.patch,
> 0001-KYLIN-3119-add-test-cases.patch, 01.PNG, 02.PNG
>
>
> in the function 'massageSql' of 'QueryUtil.java',there are a few bugs:
> 01:
> {code:java}
> while (sql.endsWith(";"))
> sql = sql.substring(0, sql.length() - 1);
> {code}
> if the sql end with ';' and after the ';' still has comments,will be
> error.Because the sql will add ("\nLIMIT " + limit) at the end.
> 02:
> {code:java}
> if (limit > 0 && !sql.toLowerCase().contains("limit")) {
> sql += ("\nLIMIT " + limit);
> }
> if (offset > 0 && !sql.toLowerCase().contains("offset")) {
> sql += ("\nOFFSET " + offset);
> }
> {code}
> if the sql already has word 'limit' in it,such as Alias,Subquery,Comments,the
> ‘limit’ in the Input box will be invalid.
> for example,the sql has subquery,and there is 'limit' in subquery.
> {code:java}
> select KYLIN_SALES.PART_DT, count(KYLIN_SALES.PRICE)
> from KYLIN_SALES
> inner join (select ACCOUNT_ID, ACCOUNT_BUYER_LEVEL from KYLIN_ACCOUNT where
> ACCOUNT_COUNTRY = 'US' limit 1) as TT
> on KYLIN_SALES.BUYER_ID = TT.ACCOUNT_ID
> group by KYLIN_SALES.PART_DT
> {code}
> the ‘limit’ in the Input box will be invalid.please refer to 01.png and
> 02.png.
> 03:
> {code:java}
> // https://issues.apache.org/jira/browse/KYLIN-2649
> if (kylinConfig.getForceLimit() > 0 &&
> !sql.toLowerCase().contains("limit")
> && sql.toLowerCase().contains("*")) {
> sql += ("\nLIMIT " + kylinConfig.getForceLimit());
> }
> {code}
> Because KYLIN-2649 is still unresolved,so I didn't change the code,but it
> has same 'limit' word bugs like above.
> And there are some situations that the sql contains \*,such as
> {code:java}count(*),kylin_sales.*{code}
> Maybe the \* in subquery too.
> it seems improperly to deal with the sql just use {code:java}
> sql.toLowerCase().contains("*")
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-2887) Subquery columns not exported in OLAPContext allColumns
[ https://issues.apache.org/jira/browse/KYLIN-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16307694#comment-16307694 ] Roger Shi commented on KYLIN-2887: -- Fixed in commit b15164ac23280ebad4e1ef92c637e070ea47b016 > Subquery columns not exported in OLAPContext allColumns > --- > > Key: KYLIN-2887 > URL: https://issues.apache.org/jira/browse/KYLIN-2887 > Project: Kylin > Issue Type: Bug >Reporter: Roger Shi > Fix For: v2.3.0 > > > Query like this returns empty value, because olap context allColumns field > isn't set rightly. > ```sql > select c.COUNTRY, c.NAME,b.TRANS_ID, b.BUYER_ID from KYLIN_COUNTRY c join ( > select * from KYLIN_SALES s join KYLIN_ACCOUNT a on s.SELLER_ID = > a.ACCOUNT_ID where a.ACCOUNT_ID <= 1866 >) b on b.ACCOUNT_COUNTRY = c.COUNTRY > ``` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2887) Subquery columns not exported in OLAPContext allColumns
[ https://issues.apache.org/jira/browse/KYLIN-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2887. -- Resolution: Fixed Fix Version/s: v2.3.0 > Subquery columns not exported in OLAPContext allColumns > --- > > Key: KYLIN-2887 > URL: https://issues.apache.org/jira/browse/KYLIN-2887 > Project: Kylin > Issue Type: Bug >Reporter: Roger Shi > Fix For: v2.3.0 > > > Query like this returns empty value, because olap context allColumns field > isn't set rightly. > ```sql > select c.COUNTRY, c.NAME,b.TRANS_ID, b.BUYER_ID from KYLIN_COUNTRY c join ( > select * from KYLIN_SALES s join KYLIN_ACCOUNT a on s.SELLER_ID = > a.ACCOUNT_ID where a.ACCOUNT_ID <= 1866 >) b on b.ACCOUNT_COUNTRY = c.COUNTRY > ``` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2771) Turn on all TIMEDATE FUNCTIONS in ODBC
[ https://issues.apache.org/jira/browse/KYLIN-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2771. -- Resolution: Fixed Fix Version/s: v2.2.0 fixed in commit 631fe416cb60223c5f96325fda40abbea24cff3b > Turn on all TIMEDATE FUNCTIONS in ODBC > -- > > Key: KYLIN-2771 > URL: https://issues.apache.org/jira/browse/KYLIN-2771 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi > Fix For: v2.2.0 > > > Only 4 functions are declared in ODBC while actually there's no such > limitation in Kylin implementation. Turn them on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2850) Throw clear error message when there're more than 63 columns in rowkey
[ https://issues.apache.org/jira/browse/KYLIN-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2850. -- Resolution: Fixed Fix Version/s: v2.2.0 fixed in fae56af2166ac21b5737542ca4c9ad1fb5b7622b > Throw clear error message when there're more than 63 columns in rowkey > -- > > Key: KYLIN-2850 > URL: https://issues.apache.org/jira/browse/KYLIN-2850 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Priority: Minor > Fix For: v2.2.0 > > > Now the error message is not that clear when there're more than 63 columns in > rowkey. Provide clearer error message in this case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2785) Handle Maprfs schema working directory
[ https://issues.apache.org/jira/browse/KYLIN-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2785. -- Resolution: Fixed Assignee: Roger Shi Fix Version/s: v2.2.0 Fixed in commit 5008866f41efd13ce5abaf8cc19c09919fe698dd > Handle Maprfs schema working directory > -- > > Key: KYLIN-2785 > URL: https://issues.apache.org/jira/browse/KYLIN-2785 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Assignee: Roger Shi >Priority: Minor > Fix For: v2.2.0 > > > Working directory starting with "maprfs" always return "maprfs:/fileXXX/xxx", > even setting "maprfs:///fileXXX/xxx" in kylin.properties file. The behavior > is different from HDFS. Inserting the two missing slash will fix it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3067) Provide web interface for dimension capping feature
Roger Shi created KYLIN-3067: Summary: Provide web interface for dimension capping feature Key: KYLIN-3067 URL: https://issues.apache.org/jira/browse/KYLIN-3067 Project: Kylin Issue Type: Improvement Components: Web Reporter: Roger Shi Assignee: Zhong,Jason As [KYLIN-2363] has provided the dimension capping feature in the backend, we need a proper web interface. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2363) Prune cuboids by capping number of dimensions
[
https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Shi resolved KYLIN-2363.
--
Resolution: Fixed
> Prune cuboids by capping number of dimensions
> -
>
> Key: KYLIN-2363
> URL: https://issues.apache.org/jira/browse/KYLIN-2363
> Project: Kylin
> Issue Type: Improvement
>Reporter: fengYu
>Assignee: Roger Shi
> Fix For: v2.3.0
>
> Attachments: Dimension Capping.md
>
>
> the scene like this:
> I have 20+ dimensions, However the query will only use at most 5 dimensions
> in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid)
> is useless.
> I think we can add a configuration in cube, which limit the max dimensions
> that cuboid includes.
> What's more, we can config which level(number of dimension) need to
> calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+
> =
> The dimension capping is turned on by adding dim_cap property in
> aggregation_groups definition.
> For example, the following aggregation group sets the dimension cap to 3. All
> cuboids containing more than 3 dimensions are skipped in this aggregation
> group.
> {code:none}
> "aggregation_groups" : [ {
> "includes" : [ "PART_DT", "META_CATEG_NAME", "CATEG_LVL2_NAME",
> "CATEG_LVL3_NAME", "LEAF_CATEG_ID", "LSTG_FORMAT_NAME", "LSTG_SITE_ID",
> "OPS_USER_ID", "OPS_REGION",
>"BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL",
> "SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL", "BUYER_ACCOUNT.ACCOUNT_COUNTRY",
> "SELLER_ACCOUNT.ACCOUNT_COUNTRY", "BUYER_COUNTRY.NAME", "SELLER_COUNTRY.NAME"
> ],
> "select_rule" : {
> "hierarchy_dims" : [ [ "META_CATEG_NAME", "CATEG_LVL2_NAME",
> "CATEG_LVL3_NAME", "LEAF_CATEG_ID" ] ],
> "mandatory_dims" : [ "PART_DT" ],
> "joint_dims" : [ [ "BUYER_ACCOUNT.ACCOUNT_COUNTRY",
> "BUYER_COUNTRY.NAME" ], [ "SELLER_ACCOUNT.ACCOUNT_COUNTRY",
> "SELLER_COUNTRY.NAME" ],
>[ "BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL",
> "SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL" ], [ "LSTG_FORMAT_NAME", "LSTG_SITE_ID"
> ], [ "OPS_USER_ID", "OPS_REGION" ] ],
> "dim_cap" : 3
> }
> } ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KYLIN-2363) Prune cuboids by capping number of dimensions
[
https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Shi updated KYLIN-2363:
-
Description:
the scene like this:
I have 20+ dimensions, However the query will only use at most 5 dimensions in
all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) is
useless.
I think we can add a configuration in cube, which limit the max dimensions that
cuboid includes.
What's more, we can config which level(number of dimension) need to calculate.
in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+
=
The dimension capping is turned on by adding dim_cap property in
aggregation_groups definition.
For example, the following aggregation group sets the dimension cap to 3. All
cuboids containing more than 3 dimensions are skipped in this aggregation
group.
{code:none}
"aggregation_groups" : [ {
"includes" : [ "PART_DT", "META_CATEG_NAME", "CATEG_LVL2_NAME",
"CATEG_LVL3_NAME", "LEAF_CATEG_ID", "LSTG_FORMAT_NAME", "LSTG_SITE_ID",
"OPS_USER_ID", "OPS_REGION",
"BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL",
"SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL", "BUYER_ACCOUNT.ACCOUNT_COUNTRY",
"SELLER_ACCOUNT.ACCOUNT_COUNTRY", "BUYER_COUNTRY.NAME", "SELLER_COUNTRY.NAME" ],
"select_rule" : {
"hierarchy_dims" : [ [ "META_CATEG_NAME", "CATEG_LVL2_NAME",
"CATEG_LVL3_NAME", "LEAF_CATEG_ID" ] ],
"mandatory_dims" : [ "PART_DT" ],
"joint_dims" : [ [ "BUYER_ACCOUNT.ACCOUNT_COUNTRY", "BUYER_COUNTRY.NAME"
], [ "SELLER_ACCOUNT.ACCOUNT_COUNTRY", "SELLER_COUNTRY.NAME" ],
[ "BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL",
"SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL" ], [ "LSTG_FORMAT_NAME", "LSTG_SITE_ID"
], [ "OPS_USER_ID", "OPS_REGION" ] ],
"dim_cap" : 3
}
} ]
{code}
was:
the scene like this:
I have 20+ dimensions, However the query will only use at most 5 dimensions in
all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) is
useless.
I think we can add a configuration in cube, which limit the max dimensions that
cuboid includes.
What's more, we can config which level(number of dimension) need to calculate.
in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+
> Prune cuboids by capping number of dimensions
> -
>
> Key: KYLIN-2363
> URL: https://issues.apache.org/jira/browse/KYLIN-2363
> Project: Kylin
> Issue Type: Improvement
>Reporter: fengYu
>Assignee: Roger Shi
> Fix For: v2.3.0
>
> Attachments: Dimension Capping.md
>
>
> the scene like this:
> I have 20+ dimensions, However the query will only use at most 5 dimensions
> in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid)
> is useless.
> I think we can add a configuration in cube, which limit the max dimensions
> that cuboid includes.
> What's more, we can config which level(number of dimension) need to
> calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+
> =
> The dimension capping is turned on by adding dim_cap property in
> aggregation_groups definition.
> For example, the following aggregation group sets the dimension cap to 3. All
> cuboids containing more than 3 dimensions are skipped in this aggregation
> group.
> {code:none}
> "aggregation_groups" : [ {
> "includes" : [ "PART_DT", "META_CATEG_NAME", "CATEG_LVL2_NAME",
> "CATEG_LVL3_NAME", "LEAF_CATEG_ID", "LSTG_FORMAT_NAME", "LSTG_SITE_ID",
> "OPS_USER_ID", "OPS_REGION",
>"BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL",
> "SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL", "BUYER_ACCOUNT.ACCOUNT_COUNTRY",
> "SELLER_ACCOUNT.ACCOUNT_COUNTRY", "BUYER_COUNTRY.NAME", "SELLER_COUNTRY.NAME"
> ],
> "select_rule" : {
> "hierarchy_dims" : [ [ "META_CATEG_NAME", "CATEG_LVL2_NAME",
> "CATEG_LVL3_NAME", "LEAF_CATEG_ID" ] ],
> "mandatory_dims" : [ "PART_DT" ],
> "joint_dims" : [ [ "BUYER_ACCOUNT.ACCOUNT_COUNTRY",
> "BUYER_COUNTRY.NAME" ], [ "SELLER_ACCOUNT.ACCOUNT_COUNTRY",
> "SELLER_COUNTRY.NAME" ],
>[ "BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL",
> "SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL" ], [ "LSTG_FORMAT_NAME", "LSTG_SITE_ID"
> ], [ "OPS_USER_ID", "OPS_REGION" ] ],
> "dim_cap" : 3
> }
> } ]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2363) Prune cuboids by capping number of dimensions
[ https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16270288#comment-16270288 ] Roger Shi commented on KYLIN-2363: -- [~Shaofengshi] Thanks for your kind remind. I'll update it in the description. > Prune cuboids by capping number of dimensions > - > > Key: KYLIN-2363 > URL: https://issues.apache.org/jira/browse/KYLIN-2363 > Project: Kylin > Issue Type: Improvement >Reporter: fengYu >Assignee: Roger Shi > Fix For: v2.3.0 > > Attachments: Dimension Capping.md > > > the scene like this: > I have 20+ dimensions, However the query will only use at most 5 dimensions > in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) > is useless. > I think we can add a configuration in cube, which limit the max dimensions > that cuboid includes. > What's more, we can config which level(number of dimension) need to > calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KYLIN-3036) Allow complex column type when loading source table
[ https://issues.apache.org/jira/browse/KYLIN-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi reassigned KYLIN-3036: Assignee: Roger Shi > Allow complex column type when loading source table > --- > > Key: KYLIN-3036 > URL: https://issues.apache.org/jira/browse/KYLIN-3036 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Assignee: Roger Shi >Priority: Minor > > Sometimes users define complex type such as array type in the table, we > should allow them to import the table if they don't use these complex type > columns in the model and cube. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-3036) Allow complex column type when loading source table
Roger Shi created KYLIN-3036: Summary: Allow complex column type when loading source table Key: KYLIN-3036 URL: https://issues.apache.org/jira/browse/KYLIN-3036 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Priority: Minor Sometimes users define complex type such as array type in the table, we should allow them to import the table if they don't use these complex type columns in the model and cube. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2773) Should not push down join condition related columns are compatible while not consistent
[
https://issues.apache.org/jira/browse/KYLIN-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226471#comment-16226471
]
Roger Shi commented on KYLIN-2773:
--
A little modification is applied on the patch, but the main logic is the same.
> Should not push down join condition related columns are compatible while not
> consistent
> ---
>
> Key: KYLIN-2773
> URL: https://issues.apache.org/jira/browse/KYLIN-2773
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
> Fix For: v2.2.0
>
> Attachments: APACHE-KYLIN-2773.patch
>
>
> For sql,
> {code}
> select PART_DT, META_CATEG_NAME, sum(price)
> from KYLIN_SALES
> INNER JOIN KYLIN_CATEGORY_GROUPINGS ON KYLIN_SALES.LEAF_CATEG_ID =
> KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID
> AND KYLIN_SALES.LSTG_SITE_ID = KYLIN_CATEGORY_GROUPINGS.SITE_ID
> INNER JOIN KYLIN_CAL_DT ON KYLIN_SALES.PART_DT = KYLIN_CAL_DT.CAL_DT
> group by PART_DT, META_CATEG_NAME
> order by PART_DT, META_CATEG_NAME
> {code}
> the datatype of KYLIN_SALES.LEAF_CATEG_ID is bigint, while the one of
> KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID is integer.
> Then the plan transformed by kylin is as follows:
> {code}
> OLAPToEnumerableConverter
> OLAPLimitRel(fetch=[5])
> OLAPSortRel(sort0=[$0], sort1=[$1], dir0=[ASC], dir1=[ASC])
> OLAPAggregateRel(group=[{0, 1}], EXPR$2=[SUM($2)])
> OLAPProjectRel(PART_DT=[$0], META_CATEG_NAME=[$16], PRICE=[$5])
> OLAPJoinRel(condition=[=($0, $19)], joinType=[inner])
> {code}
> {color:#f79232}
> {code}
> OLAPProjectRel(expr#0..19=[{inputs}], PART_DT=[$t0],
> LSTG_FORMAT_NAME=[$t1], SLR_SEGMENT_CD=[$t2], LEAF_CATEG_ID=[$t3],
> LSTG_SITE_ID=[$t4], PRICE=[$t5], SELLER_ID=[$t6], COUNT__=[$t7],
> MIN_PRICE_=[$t8], COUNT_DISTINCT_SELLER_ID_=[$t9],
> USER_DEFINED_FIELD1=[$t10], USER_DEFINED_FIELD3=[$t11], UPD_DATE=[$t12],
> UPD_USER=[$t13], LEAF_CATEG_ID0=[$t14], SITE_ID=[$t15],
> META_CATEG_NAME=[$t16], CATEG_LVL2_NAME=[$t17], CATEG_LVL3_NAME=[$t18])
> OLAPJoinRel(condition=[AND(=($3, $19), =($4, $15))],
> joinType=[inner])
> OLAPTableScan(table=[[DEFAULT, KYLIN_SALES]], fields=[[0, 1,
> 2, 3, 4, 5, 6, 7, 8, 9]])
> OLAPProjectRel(expr#0..8=[{inputs}],
> expr#9=[CAST($t4):BIGINT], USER_DEFINED_FIELD1=[$t0],
> USER_DEFINED_FIELD3=[$t1], UPD_DATE=[$t2], UPD_USER=[$t3],
> LEAF_CATEG_ID=[$t4], SITE_ID=[$t5], META_CATEG_NAME=[$t6],
> CATEG_LVL2_NAME=[$t7], CATEG_LVL3_NAME=[$t8], LEAF_CATEG_ID9=[$t9])
> {code}
> {color}
> {code}
> OLAPTableScan(table=[[DEFAULT, KYLIN_CATEGORY_GROUPINGS]],
> fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8]])
> OLAPTableScan(table=[[DEFAULT, KYLIN_CAL_DT]], fields=[[0, 1, 2,
> 3]])
> {code}
> However, what we expect is as follows:
> {code}
> OLAPToEnumerableConverter
> OLAPLimitRel(fetch=[5])
> OLAPSortRel(sort0=[$0], sort1=[$1], dir0=[ASC], dir1=[ASC])
> OLAPAggregateRel(group=[{0, 1}], EXPR$2=[SUM($2)])
> OLAPProjectRel(expr#0..21=[{inputs}], PART_DT=[$t0],
> META_CATEG_NAME=[$t17], PRICE=[$t4])
> OLAPJoinRel(condition=[=($0, $19)], joinType=[inner])
> {code}
> {color:#f79232}
> {code}
> OLAPJoinRel(condition=[AND(=($2, $10), =($3, $11))],
> joinType=[inner])
> OLAPTableScan(table=[[DEFAULT, KYLIN_SALES]], fields=[[0, 1, 2,
> 3, 4, 5, 6, 7, 8, 9]])
> {code}
> {color}
> {code}
> OLAPTableScan(table=[[DEFAULT, KYLIN_CATEGORY_GROUPINGS]],
> fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8]])
> OLAPTableScan(table=[[DEFAULT, KYLIN_CAL_DT]], fields=[[0, 1, 2,
> 3, 4]])
> {code}
> The reason for this difference is as follows:
> * Although we remove the {{JoinPushExpressionsRule}} in {{OLAPTableScan}},
> the method {{RelOptUtil.pushDownJoinConditions()}} is still invoked when
> creating a join in {{SqlToRelConverter}}.
> * In the method of {{RelOptUtil.pushDownJoinConditions()}}, since the
> datatypes of the join related columns are not the same, *cast* function will
> be automatically assigned to KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID. Then a
> {{OLAPProjectRel}} will be introduced.
> In kylin, we don't need {{RelOptUtil.pushDownJoinConditions()}}. Therefore,
> the solution for this is just remove that logic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KYLIN-2930) Selecting one column in union causes compile error
Roger Shi created KYLIN-2930:
Summary: Selecting one column in union causes compile error
Key: KYLIN-2930
URL: https://issues.apache.org/jira/browse/KYLIN-2930
Project: Kylin
Issue Type: Bug
Reporter: Roger Shi
Query like
{code:sql}
select count(*) as cnt from TEST_KYLIN_FACT where TRANS_ID < 1000 union select
count(*) as cnt from TEST_KYLIN_FACT where TRANS_ID > 9000
{code}
make kylin throw exception:
{code:java}
Error while executing SQL "select count() from KYLIN_SALES union select count()
from KYLIN_SALES LIMIT 5": Error while compiling generated Java code:
public static class Record1_0 implements java.io.Serializable { public long f0;
public Record1_0() {} public boolean equals(Object o) { if (this == o) { return
true; } if (!(o instanceof Record1_0)) { return false; } return this.f0 ==
((Record1_0) o).f0; } public int hashCode() { int h = 0; h =
org.apache.calcite.runtime.Utilities.hash(h, this.f0); return h; } public int
compareTo(Record1_0 that) { final int c; c =
org.apache.calcite.runtime.Utilities.compare(this.f0, that.f0); if (c != 0) {
return c; } return 0; } public String toString() { return "{f0=" + this.f0 +
"}"; } } org.apache.calcite.DataContext root; public
org.apache.calcite.linq4j.Enumerable bind(final org.apache.calcite.DataContext
root0) { root = root0; final org.apache.calcite.linq4j.Enumerable
_inputEnumerable = ((org.apache.kylin.query.schema.OLAPTable)
root.getRootSchema().getSubSchema("DEFAULT").getTable("KYLIN_SALES")).executeOLAPQuery(root,
1); final org.apache.calcite.linq4j.AbstractEnumerable child = new
org.apache.calcite.linq4j.AbstractEnumerable(){ public
org.apache.calcite.linq4j.Enumerator enumerator() { return new
org.apache.calcite.linq4j.Enumerator(){ public final
org.apache.calcite.linq4j.Enumerator inputEnumerator =
_inputEnumerable.enumerator(); public void reset() { inputEnumerator.reset(); }
public boolean moveNext() { return inputEnumerator.moveNext(); } public void
close() { inputEnumerator.close(); } public Object current() { return
org.apache.calcite.runtime.SqlFunctions.toLong(((Object[])
inputEnumerator.current())[10]); } }; } }; final
org.apache.calcite.linq4j.Enumerable _inputEnumerable0 =
((org.apache.kylin.query.schema.OLAPTable)
root.getRootSchema().getSubSchema("DEFAULT").getTable("KYLIN_SALES")).executeOLAPQuery(root,
2); final org.apache.calcite.linq4j.AbstractEnumerable child1 = new
org.apache.calcite.linq4j.AbstractEnumerable(){ public
org.apache.calcite.linq4j.Enumerator enumerator() { return new
org.apache.calcite.linq4j.Enumerator(){ public final
org.apache.calcite.linq4j.Enumerator inputEnumerator =
inputEnumerable0.enumerator(); public void reset() { inputEnumerator.reset(); }
public boolean moveNext() { return inputEnumerator.moveNext(); } public void
close() { inputEnumerator.close(); } public Object current() { return
((Record12_1) inputEnumerator.current()).KY_COUNT; } }; } }; return
org.apache.calcite.linq4j.Linq4j.singletonEnumerable(child.aggregate(new
org.apache.calcite.linq4j.function.Function0() { public Object apply() { long
a0s0; a0s0 = 0; Record1_0 record0; record0 = new Record1_0(); record0.f0 =
a0s0; return record0; } } .apply(), new
org.apache.calcite.linq4j.function.Function2() { public Record1_0
apply(Record1_0 acc, long in) { acc.f0 = acc.f0 + in; return acc; } public
Record1_0 apply(Record1_0 acc, Long in) { return apply( acc, in.longValue()); }
public Record1_0 apply(Object acc, Object in) { return apply( (Record1_0) acc,
(Long) in); } } , new org.apache.calcite.linq4j.function.Function1() { public
long apply(Record1_0 acc) { return acc.f0; } public Object apply(Object acc) {
return apply( (Record1_0) acc); } }
)).union(org.apache.calcite.linq4j.Linq4j.singletonEnumerable(child1.aggregate(new
org.apache.calcite.linq4j.function.Function0() { public Object apply() { long
a0s0; a0s0 = 0; Record1_0 record0; record0 = new Record1_0(); record0.f0 =
a0s0; return record0; } } .apply(), new
org.apache.calcite.linq4j.function.Function2() { public Record1_0
apply(Record1_0 acc, long in) { acc.f0 = acc.f0 + in; return acc; } public
Record1_0 apply(Record1_0 acc, Long in) { return apply( acc, in.longValue()); }
public Record1_0 apply(Object acc, Object in) { return apply( (Record1_0) acc,
(Long) in); } } , new org.apache.calcite.linq4j.function.Function1() { public
long apply(Record1_0 acc) { return acc.f0; } public Object apply(Object acc) {
return apply( (Record1_0) acc); } } ))).take(5); } public Class
getElementType() { return long.class; }
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KYLIN-2887) Subquery columns not exported in OLAPContext allColumns
Roger Shi created KYLIN-2887: Summary: Subquery columns not exported in OLAPContext allColumns Key: KYLIN-2887 URL: https://issues.apache.org/jira/browse/KYLIN-2887 Project: Kylin Issue Type: Bug Reporter: Roger Shi Query like this returns empty value, because olap context allColumns field isn't set rightly. ```sql select c.COUNTRY, c.NAME,b.TRANS_ID, b.BUYER_ID from KYLIN_COUNTRY c join ( select * from KYLIN_SALES s join KYLIN_ACCOUNT a on s.SELLER_ID = a.ACCOUNT_ID where a.ACCOUNT_ID <= 1866 ) b on b.ACCOUNT_COUNTRY = c.COUNTRY ``` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2773) Should not push down join condition related columns are compatible while not consistent
[
https://issues.apache.org/jira/browse/KYLIN-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Shi resolved KYLIN-2773.
--
Resolution: Fixed
> Should not push down join condition related columns are compatible while not
> consistent
> ---
>
> Key: KYLIN-2773
> URL: https://issues.apache.org/jira/browse/KYLIN-2773
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
> Fix For: v2.2.0
>
> Attachments: APACHE-KYLIN-2773.patch
>
>
> For sql,
> {code}
> select PART_DT, META_CATEG_NAME, sum(price)
> from KYLIN_SALES
> INNER JOIN KYLIN_CATEGORY_GROUPINGS ON KYLIN_SALES.LEAF_CATEG_ID =
> KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID
> AND KYLIN_SALES.LSTG_SITE_ID = KYLIN_CATEGORY_GROUPINGS.SITE_ID
> INNER JOIN KYLIN_CAL_DT ON KYLIN_SALES.PART_DT = KYLIN_CAL_DT.CAL_DT
> group by PART_DT, META_CATEG_NAME
> order by PART_DT, META_CATEG_NAME
> {code}
> the datatype of KYLIN_SALES.LEAF_CATEG_ID is bigint, while the one of
> KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID is integer.
> Then the plan transformed by kylin is as follows:
> {code}
> OLAPToEnumerableConverter
> OLAPLimitRel(fetch=[5])
> OLAPSortRel(sort0=[$0], sort1=[$1], dir0=[ASC], dir1=[ASC])
> OLAPAggregateRel(group=[{0, 1}], EXPR$2=[SUM($2)])
> OLAPProjectRel(PART_DT=[$0], META_CATEG_NAME=[$16], PRICE=[$5])
> OLAPJoinRel(condition=[=($0, $19)], joinType=[inner])
> {code}
> {color:#f79232}
> {code}
> OLAPProjectRel(expr#0..19=[{inputs}], PART_DT=[$t0],
> LSTG_FORMAT_NAME=[$t1], SLR_SEGMENT_CD=[$t2], LEAF_CATEG_ID=[$t3],
> LSTG_SITE_ID=[$t4], PRICE=[$t5], SELLER_ID=[$t6], COUNT__=[$t7],
> MIN_PRICE_=[$t8], COUNT_DISTINCT_SELLER_ID_=[$t9],
> USER_DEFINED_FIELD1=[$t10], USER_DEFINED_FIELD3=[$t11], UPD_DATE=[$t12],
> UPD_USER=[$t13], LEAF_CATEG_ID0=[$t14], SITE_ID=[$t15],
> META_CATEG_NAME=[$t16], CATEG_LVL2_NAME=[$t17], CATEG_LVL3_NAME=[$t18])
> OLAPJoinRel(condition=[AND(=($3, $19), =($4, $15))],
> joinType=[inner])
> OLAPTableScan(table=[[DEFAULT, KYLIN_SALES]], fields=[[0, 1,
> 2, 3, 4, 5, 6, 7, 8, 9]])
> OLAPProjectRel(expr#0..8=[{inputs}],
> expr#9=[CAST($t4):BIGINT], USER_DEFINED_FIELD1=[$t0],
> USER_DEFINED_FIELD3=[$t1], UPD_DATE=[$t2], UPD_USER=[$t3],
> LEAF_CATEG_ID=[$t4], SITE_ID=[$t5], META_CATEG_NAME=[$t6],
> CATEG_LVL2_NAME=[$t7], CATEG_LVL3_NAME=[$t8], LEAF_CATEG_ID9=[$t9])
> {code}
> {color}
> {code}
> OLAPTableScan(table=[[DEFAULT, KYLIN_CATEGORY_GROUPINGS]],
> fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8]])
> OLAPTableScan(table=[[DEFAULT, KYLIN_CAL_DT]], fields=[[0, 1, 2,
> 3]])
> {code}
> However, what we expect is as follows:
> {code}
> OLAPToEnumerableConverter
> OLAPLimitRel(fetch=[5])
> OLAPSortRel(sort0=[$0], sort1=[$1], dir0=[ASC], dir1=[ASC])
> OLAPAggregateRel(group=[{0, 1}], EXPR$2=[SUM($2)])
> OLAPProjectRel(expr#0..21=[{inputs}], PART_DT=[$t0],
> META_CATEG_NAME=[$t17], PRICE=[$t4])
> OLAPJoinRel(condition=[=($0, $19)], joinType=[inner])
> {code}
> {color:#f79232}
> {code}
> OLAPJoinRel(condition=[AND(=($2, $10), =($3, $11))],
> joinType=[inner])
> OLAPTableScan(table=[[DEFAULT, KYLIN_SALES]], fields=[[0, 1, 2,
> 3, 4, 5, 6, 7, 8, 9]])
> {code}
> {color}
> {code}
> OLAPTableScan(table=[[DEFAULT, KYLIN_CATEGORY_GROUPINGS]],
> fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8]])
> OLAPTableScan(table=[[DEFAULT, KYLIN_CAL_DT]], fields=[[0, 1, 2,
> 3, 4]])
> {code}
> The reason for this difference is as follows:
> * Although we remove the {{JoinPushExpressionsRule}} in {{OLAPTableScan}},
> the method {{RelOptUtil.pushDownJoinConditions()}} is still invoked when
> creating a join in {{SqlToRelConverter}}.
> * In the method of {{RelOptUtil.pushDownJoinConditions()}}, since the
> datatypes of the join related columns are not the same, *cast* function will
> be automatically assigned to KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID. Then a
> {{OLAPProjectRel}} will be introduced.
> In kylin, we don't need {{RelOptUtil.pushDownJoinConditions()}}. Therefore,
> the solution for this is just remove that logic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KYLIN-2850) Throw clear error message when there're more than 63 columns in rowkey
Roger Shi created KYLIN-2850: Summary: Throw clear error message when there're more than 63 columns in rowkey Key: KYLIN-2850 URL: https://issues.apache.org/jira/browse/KYLIN-2850 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Priority: Minor Now the error message is not that clear when there're more than 63 columns in rowkey. Provide clearer error message in this case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2830) Union two subquery under join make SQL return null values
[
https://issues.apache.org/jira/browse/KYLIN-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Shi updated KYLIN-2830:
-
Description:
SQL like:
{code:sql}
select sum(TEST_A.PRICE) as ITEM_CNT
FROM TEST_KYLIN_FACT as TEST_A
join (
select * from TEST_KYLIN_FACT where CAL_DT < DATE '2012-06-01'
union
select * from TEST_KYLIN_FACT where CAL_DT > DATE '2013-06-01'
) TEST_B
on TEST_A.TRANS_ID = TEST_B.TRANS_ID
group by TEST_A.SELLER_ID
{code}
returns null values.
was:
SQL like:
{code:sql}
select sum(TEST_A.PRICE) as ITEM_CNT
FROM TEST_KYLIN_FACT as TEST_A
join (
select * from ITEM_CNT where CAL_DT < DATE '2012-06-01'
union
select * from ITEM_CNT where CAL_DT > DATE '2013-06-01'
) TEST_B
on TEST_A.TRANS_ID = TEST_B.TRANS_ID
group by TEST_A.SELLER_ID
{code}
returns null values.
> Union two subquery under join make SQL return null values
> -
>
> Key: KYLIN-2830
> URL: https://issues.apache.org/jira/browse/KYLIN-2830
> Project: Kylin
> Issue Type: Bug
>Reporter: Roger Shi
>
> SQL like:
> {code:sql}
> select sum(TEST_A.PRICE) as ITEM_CNT
> FROM TEST_KYLIN_FACT as TEST_A
> join (
> select * from TEST_KYLIN_FACT where CAL_DT < DATE '2012-06-01'
> union
> select * from TEST_KYLIN_FACT where CAL_DT > DATE '2013-06-01'
> ) TEST_B
> on TEST_A.TRANS_ID = TEST_B.TRANS_ID
> group by TEST_A.SELLER_ID
> {code}
> returns null values.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KYLIN-2829) Union two subquery under join make SQL return null values
Roger Shi created KYLIN-2829:
Summary: Union two subquery under join make SQL return null values
Key: KYLIN-2829
URL: https://issues.apache.org/jira/browse/KYLIN-2829
Project: Kylin
Issue Type: Bug
Reporter: Roger Shi
SQL like:
{code:sql}
select sum(TEST_A.PRICE) as ITEM_CNT
FROM TEST_KYLIN_FACT as TEST_A
join (
select * from ITEM_CNT where CAL_DT < DATE '2012-06-01'
union
select * from ITEM_CNT where CAL_DT > DATE '2013-06-01'
) TEST_B
on TEST_A.TRANS_ID = TEST_B.TRANS_ID
group by TEST_A.SELLER_ID
{code}
returns null values.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KYLIN-2830) Union two subquery under join make SQL return null values
Roger Shi created KYLIN-2830:
Summary: Union two subquery under join make SQL return null values
Key: KYLIN-2830
URL: https://issues.apache.org/jira/browse/KYLIN-2830
Project: Kylin
Issue Type: Bug
Reporter: Roger Shi
SQL like:
{code:sql}
select sum(TEST_A.PRICE) as ITEM_CNT
FROM TEST_KYLIN_FACT as TEST_A
join (
select * from ITEM_CNT where CAL_DT < DATE '2012-06-01'
union
select * from ITEM_CNT where CAL_DT > DATE '2013-06-01'
) TEST_B
on TEST_A.TRANS_ID = TEST_B.TRANS_ID
group by TEST_A.SELLER_ID
{code}
returns null values.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KYLIN-2773) Should not push down join condition related columns are compatible while not consistent
[
https://issues.apache.org/jira/browse/KYLIN-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144964#comment-16144964
]
Roger Shi commented on KYLIN-2773:
--
Thank you for the patch, [~yaho]. I'll merge it.
> Should not push down join condition related columns are compatible while not
> consistent
> ---
>
> Key: KYLIN-2773
> URL: https://issues.apache.org/jira/browse/KYLIN-2773
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
> Fix For: v2.2.0
>
> Attachments: APACHE-KYLIN-2773.patch
>
>
> For sql,
> {code}
> select PART_DT, META_CATEG_NAME, sum(price)
> from KYLIN_SALES
> INNER JOIN KYLIN_CATEGORY_GROUPINGS ON KYLIN_SALES.LEAF_CATEG_ID =
> KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID
> AND KYLIN_SALES.LSTG_SITE_ID = KYLIN_CATEGORY_GROUPINGS.SITE_ID
> INNER JOIN KYLIN_CAL_DT ON KYLIN_SALES.PART_DT = KYLIN_CAL_DT.CAL_DT
> group by PART_DT, META_CATEG_NAME
> order by PART_DT, META_CATEG_NAME
> {code}
> the datatype of KYLIN_SALES.LEAF_CATEG_ID is bigint, while the one of
> KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID is integer.
> Then the plan transformed by kylin is as follows:
> {code}
> OLAPToEnumerableConverter
> OLAPLimitRel(fetch=[5])
> OLAPSortRel(sort0=[$0], sort1=[$1], dir0=[ASC], dir1=[ASC])
> OLAPAggregateRel(group=[{0, 1}], EXPR$2=[SUM($2)])
> OLAPProjectRel(PART_DT=[$0], META_CATEG_NAME=[$16], PRICE=[$5])
> OLAPJoinRel(condition=[=($0, $19)], joinType=[inner])
> {code}
> {color:#f79232}
> {code}
> OLAPProjectRel(expr#0..19=[{inputs}], PART_DT=[$t0],
> LSTG_FORMAT_NAME=[$t1], SLR_SEGMENT_CD=[$t2], LEAF_CATEG_ID=[$t3],
> LSTG_SITE_ID=[$t4], PRICE=[$t5], SELLER_ID=[$t6], COUNT__=[$t7],
> MIN_PRICE_=[$t8], COUNT_DISTINCT_SELLER_ID_=[$t9],
> USER_DEFINED_FIELD1=[$t10], USER_DEFINED_FIELD3=[$t11], UPD_DATE=[$t12],
> UPD_USER=[$t13], LEAF_CATEG_ID0=[$t14], SITE_ID=[$t15],
> META_CATEG_NAME=[$t16], CATEG_LVL2_NAME=[$t17], CATEG_LVL3_NAME=[$t18])
> OLAPJoinRel(condition=[AND(=($3, $19), =($4, $15))],
> joinType=[inner])
> OLAPTableScan(table=[[DEFAULT, KYLIN_SALES]], fields=[[0, 1,
> 2, 3, 4, 5, 6, 7, 8, 9]])
> OLAPProjectRel(expr#0..8=[{inputs}],
> expr#9=[CAST($t4):BIGINT], USER_DEFINED_FIELD1=[$t0],
> USER_DEFINED_FIELD3=[$t1], UPD_DATE=[$t2], UPD_USER=[$t3],
> LEAF_CATEG_ID=[$t4], SITE_ID=[$t5], META_CATEG_NAME=[$t6],
> CATEG_LVL2_NAME=[$t7], CATEG_LVL3_NAME=[$t8], LEAF_CATEG_ID9=[$t9])
> {code}
> {color}
> {code}
> OLAPTableScan(table=[[DEFAULT, KYLIN_CATEGORY_GROUPINGS]],
> fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8]])
> OLAPTableScan(table=[[DEFAULT, KYLIN_CAL_DT]], fields=[[0, 1, 2,
> 3]])
> {code}
> However, what we expect is as follows:
> {code}
> OLAPToEnumerableConverter
> OLAPLimitRel(fetch=[5])
> OLAPSortRel(sort0=[$0], sort1=[$1], dir0=[ASC], dir1=[ASC])
> OLAPAggregateRel(group=[{0, 1}], EXPR$2=[SUM($2)])
> OLAPProjectRel(expr#0..21=[{inputs}], PART_DT=[$t0],
> META_CATEG_NAME=[$t17], PRICE=[$t4])
> OLAPJoinRel(condition=[=($0, $19)], joinType=[inner])
> {code}
> {color:#f79232}
> {code}
> OLAPJoinRel(condition=[AND(=($2, $10), =($3, $11))],
> joinType=[inner])
> OLAPTableScan(table=[[DEFAULT, KYLIN_SALES]], fields=[[0, 1, 2,
> 3, 4, 5, 6, 7, 8, 9]])
> {code}
> {color}
> {code}
> OLAPTableScan(table=[[DEFAULT, KYLIN_CATEGORY_GROUPINGS]],
> fields=[[0, 1, 2, 3, 4, 5, 6, 7, 8]])
> OLAPTableScan(table=[[DEFAULT, KYLIN_CAL_DT]], fields=[[0, 1, 2,
> 3, 4]])
> {code}
> The reason for this difference is as follows:
> * Although we remove the {{JoinPushExpressionsRule}} in {{OLAPTableScan}},
> the method {{RelOptUtil.pushDownJoinConditions()}} is still invoked when
> creating a join in {{SqlToRelConverter}}.
> * In the method of {{RelOptUtil.pushDownJoinConditions()}}, since the
> datatypes of the join related columns are not the same, *cast* function will
> be automatically assigned to KYLIN_CATEGORY_GROUPINGS.LEAF_CATEG_ID. Then a
> {{OLAPProjectRel}} will be introduced.
> In kylin, we don't need {{RelOptUtil.pushDownJoinConditions()}}. Therefore,
> the solution for this is just remove that logic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KYLIN-2809) Support operator "+" as string concat operator
Roger Shi created KYLIN-2809: Summary: Support operator "+" as string concat operator Key: KYLIN-2809 URL: https://issues.apache.org/jira/browse/KYLIN-2809 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Tableau only support "+" as string concat operator. Support it will improve tableau compatibility. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2657) Cube merge TopN dictionary not found, cause NPE
[ https://issues.apache.org/jira/browse/KYLIN-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119424#comment-16119424 ] Roger Shi commented on KYLIN-2657: -- Fixed version is 2.1.0 > Cube merge TopN dictionary not found, cause NPE > --- > > Key: KYLIN-2657 > URL: https://issues.apache.org/jira/browse/KYLIN-2657 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Reporter: Roger Shi >Assignee: Roger Shi > Fix For: v2.1.0 > > > One TopN measure with two group-by columns, and both of them are in fact > table. If one cardinality is high and the other is low, merging Cube may fail > for NPE (dict not found). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2777) Should throw error when sql contains non-equi left join
Roger Shi created KYLIN-2777: Summary: Should throw error when sql contains non-equi left join Key: KYLIN-2777 URL: https://issues.apache.org/jira/browse/KYLIN-2777 Project: Kylin Issue Type: Bug Reporter: Roger Shi SQL like: select fact_table.A, lookup_table.B from fact_table fa left join lookup_table lo on fa.C = lo.D and fa.E = 'asdf' The join is non-equi left join. It's not support in Kylin data model, should throw error instead of ignore it. Current implementation leads to wrong result instead of clear error message. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (KYLIN-2772) Turn on all TIMEDATE FUNCTIONS in ODBC
[ https://issues.apache.org/jira/browse/KYLIN-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi closed KYLIN-2772. Resolution: Duplicate > Turn on all TIMEDATE FUNCTIONS in ODBC > -- > > Key: KYLIN-2772 > URL: https://issues.apache.org/jira/browse/KYLIN-2772 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi > > Only 4 functions are declared in ODBC while actually there's no such > limitation in Kylin implementation. Turn them on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2771) Turn on all TIMEDATE FUNCTIONS in ODBC
Roger Shi created KYLIN-2771: Summary: Turn on all TIMEDATE FUNCTIONS in ODBC Key: KYLIN-2771 URL: https://issues.apache.org/jira/browse/KYLIN-2771 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Only 4 functions are declared in ODBC while actually there's no such limitation in Kylin implementation. Turn them on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2772) Turn on all TIMEDATE FUNCTIONS in ODBC
Roger Shi created KYLIN-2772: Summary: Turn on all TIMEDATE FUNCTIONS in ODBC Key: KYLIN-2772 URL: https://issues.apache.org/jira/browse/KYLIN-2772 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Only 4 functions are declared in ODBC while actually there's no such limitation in Kylin implementation. Turn them on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2623) Move output(Hbase) related code from MR engine to outputside
[ https://issues.apache.org/jira/browse/KYLIN-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2623. -- Resolution: Fixed fixed in commit a38b02df0387541684aa1689e044927af650f1c7 > Move output(Hbase) related code from MR engine to outputside > > > Key: KYLIN-2623 > URL: https://issues.apache.org/jira/browse/KYLIN-2623 > Project: Kylin > Issue Type: Improvement > Environment: Output engine is extendable according to the design of > Kylin. So outputformat and reducer number should be defined in output side > instead of MR engine. Move these code to the right position will make it more > extendable. >Reporter: Roger Shi >Assignee: Roger Shi > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2657) Cube merge TopN dictionary not found, cause NPE
[ https://issues.apache.org/jira/browse/KYLIN-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2657. -- Resolution: Fixed fixed in commit 9ad0ba3ddb391695eddaadca438dc4dfdda60d5f > Cube merge TopN dictionary not found, cause NPE > --- > > Key: KYLIN-2657 > URL: https://issues.apache.org/jira/browse/KYLIN-2657 > Project: Kylin > Issue Type: Bug >Reporter: Roger Shi >Assignee: Roger Shi > > One TopN measure with two group-by columns, and both of them are in fact > table. If one cardinality is high and the other is low, merging Cube may fail > for NPE (dict not found). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2765) Eliminate restriction on Global Dictionary of Dim columns
Roger Shi created KYLIN-2765: Summary: Eliminate restriction on Global Dictionary of Dim columns Key: KYLIN-2765 URL: https://issues.apache.org/jira/browse/KYLIN-2765 Project: Kylin Issue Type: Improvement Components: Job Engine, Metadata, Query Engine Reporter: Roger Shi Assignee: Dong Li Cube dimension column is not allow to be in accurate-count-distinct measure. Global Dictionary encoding is a kind of dict in metadata. Dict encoding is created for dim at the beginning, so Global Dictionary is a special one for measure. To eliminate the restriction, there're two possible ways in my view. One is move Global Dictionary metadata out of dict section to a new section such as "measure dict" (not there now, create a new one). The other way is handle Global Dictionary differently in both cubing engine and query engine. There might be other better methods. Let's discuss here and find a good way out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2363) Prune cuboids by capping number of dimensions
[ https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15982690#comment-15982690 ] Roger Shi commented on KYLIN-2363: -- Hi, I have uploaded a design draft. Please let me know if anything not clear. Comments are more than welcome. > Prune cuboids by capping number of dimensions > - > > Key: KYLIN-2363 > URL: https://issues.apache.org/jira/browse/KYLIN-2363 > Project: Kylin > Issue Type: Improvement >Reporter: fengYu > Attachments: Dimension Capping.md > > > the scene like this: > I have 20+ dimensions, However the query will only use at most 5 dimensions > in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) > is useless. > I think we can add a configuration in cube, which limit the max dimensions > that cuboid includes. > What's more, we can config which level(number of dimension) need to > calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2363) Prune cuboids by capping number of dimensions
[ https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-2363: - Attachment: Dimension Capping.md > Prune cuboids by capping number of dimensions > - > > Key: KYLIN-2363 > URL: https://issues.apache.org/jira/browse/KYLIN-2363 > Project: Kylin > Issue Type: Improvement >Reporter: fengYu > Attachments: Dimension Capping.md > > > the scene like this: > I have 20+ dimensions, However the query will only use at most 5 dimensions > in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) > is useless. > I think we can add a configuration in cube, which limit the max dimensions > that cuboid includes. > What's more, we can config which level(number of dimension) need to > calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2538) extract(MONTH from CURRENT_DATE) cannot be selected as a column in sql
[ https://issues.apache.org/jira/browse/KYLIN-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15980337#comment-15980337 ] Roger Shi commented on KYLIN-2538: -- I suppose this query targets CI Data Model and Cube. If yes, CURRENT_DATE is not in the table. And count(*) should not in the query. The refined query is "select extract(MONTH from CAL_DT) from test_kylin_fact" and it returns the expected result. Please let me know if I miss anything. > extract(MONTH from CURRENT_DATE) cannot be selected as a column in sql > -- > > Key: KYLIN-2538 > URL: https://issues.apache.org/jira/browse/KYLIN-2538 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Reporter: Dong Li >Assignee: liyang > > This SQL will fail with exceptions: > select extract(MONTH from CURRENT_DATE), count(*) from test_kylin_fact > Error message: > Error while executing SQL "select extract(MONTH from CURRENT_DATE), count(*) > from test_kylin_fact LIMIT 5": No TblColRef found in > EXTRACT_DATE(FLAG(MONTH), Reinterpret(CURRENT_DATE)) > Stacktrace: > Caused by: java.lang.IllegalStateException: No TblColRef found in > EXTRACT_DATE(FLAG(MONTH), Reinterpret(CURRENT_DATE)) > at > org.apache.kylin.query.relnode.OLAPProjectRel.buildColumnRowType(OLAPProjectRel.java:132) > at > org.apache.kylin.query.relnode.OLAPProjectRel.implementOLAP(OLAPProjectRel.java:117) > at > org.apache.kylin.query.relnode.OLAPRel$OLAPImplementor.visitChild(OLAPRel.java:83) > at > org.apache.kylin.query.relnode.OLAPLimitRel.implementOLAP(OLAPLimitRel.java:75) > at > org.apache.kylin.query.relnode.OLAPRel$OLAPImplementor.visitChild(OLAPRel.java:83) > at > org.apache.kylin.query.relnode.OLAPToEnumerableConverter.implement(OLAPToEnumerableConverter.java:85) > at > org.apache.calcite.adapter.enumerable.EnumerableRelImplementor.implementRoot(EnumerableRelImplementor.java:108) > at > org.apache.calcite.adapter.enumerable.EnumerableInterpretable.toBindable(EnumerableInterpretable.java:92) > at > org.apache.calcite.prepare.CalcitePrepareImpl$CalcitePreparingStmt.implement(CalcitePrepareImpl.java:1248) > at org.apache.calcite.prepare.Prepare.prepareSql(Prepare.java:306) > at org.apache.calcite.prepare.Prepare.prepareSql(Prepare.java:203) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2532) Make Hive flat step more extensible
[ https://issues.apache.org/jira/browse/KYLIN-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-2532: - Description: How to import data from Hive is defined in Kylin itself. We should make it more extensible for advanced usage case. For example, if we want to control the hive records number imported to Kylin for testing, there's no injection point. Other more advanced cases also require more injection points in this step. Currently we build Hive command by appending strings in code. It might be better if we replace it with some template files proposed by [~albertoramon]. was:How to import data from Hive is defined in Kylin itself. We should make it more extensible for advanced usage case. > Make Hive flat step more extensible > --- > > Key: KYLIN-2532 > URL: https://issues.apache.org/jira/browse/KYLIN-2532 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Priority: Minor > > How to import data from Hive is defined in Kylin itself. We should make it > more extensible for advanced usage case. > For example, if we want to control the hive records number imported to Kylin > for testing, there's no injection point. Other more advanced cases also > require more injection points in this step. > Currently we build Hive command by appending strings in code. It might be > better if we replace it with some template files proposed by [~albertoramon]. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-490) Support multiple column distinct count
[ https://issues.apache.org/jira/browse/KYLIN-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-490. - Resolution: Fixed > Support multiple column distinct count > -- > > Key: KYLIN-490 > URL: https://issues.apache.org/jira/browse/KYLIN-490 > Project: Kylin > Issue Type: Improvement >Reporter: Luke Han > Labels: github-import > Attachments: > 0001-KYLIN-490-support-multiple-column-distinct-count.patch, > 0002-KYLIN-490-support-multiple-column-distinct-count.patch > > > Make count distinct(A, B) work, currently calcite only support count distinct > on one column. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/15 > Created by: [liyang-gmt8|https://github.com/liyang-gmt8] > Labels: enhancement, > Milestone: v0.6.2 Release > Assignee: [liyang-gmt8|https://github.com/liyang-gmt8] > Created at: Fri Oct 24 15:27:20 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-490) Support multiple column distinct count
[ https://issues.apache.org/jira/browse/KYLIN-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-490: Attachment: 0002-KYLIN-490-support-multiple-column-distinct-count.patch 0001-KYLIN-490-support-multiple-column-distinct-count.patch > Support multiple column distinct count > -- > > Key: KYLIN-490 > URL: https://issues.apache.org/jira/browse/KYLIN-490 > Project: Kylin > Issue Type: Improvement >Reporter: Luke Han > Labels: github-import > Attachments: > 0001-KYLIN-490-support-multiple-column-distinct-count.patch, > 0002-KYLIN-490-support-multiple-column-distinct-count.patch > > > Make count distinct(A, B) work, currently calcite only support count distinct > on one column. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/15 > Created by: [liyang-gmt8|https://github.com/liyang-gmt8] > Labels: enhancement, > Milestone: v0.6.2 Release > Assignee: [liyang-gmt8|https://github.com/liyang-gmt8] > Created at: Fri Oct 24 15:27:20 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-490) Support multiple column distinct count
[ https://issues.apache.org/jira/browse/KYLIN-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15962758#comment-15962758 ] Roger Shi commented on KYLIN-490: - Fixed in commit 636282db889973fe29269b43e417414effb68b76 88a1c71dde855c693b230f67b92c4cd067d43b2b > Support multiple column distinct count > -- > > Key: KYLIN-490 > URL: https://issues.apache.org/jira/browse/KYLIN-490 > Project: Kylin > Issue Type: Improvement >Reporter: Luke Han > Labels: github-import > > Make count distinct(A, B) work, currently calcite only support count distinct > on one column. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/15 > Created by: [liyang-gmt8|https://github.com/liyang-gmt8] > Labels: enhancement, > Milestone: v0.6.2 Release > Assignee: [liyang-gmt8|https://github.com/liyang-gmt8] > Created at: Fri Oct 24 15:27:20 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (KYLIN-2532) Make Hive flat step more extensible
[ https://issues.apache.org/jira/browse/KYLIN-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956589#comment-15956589 ] Roger Shi edited comment on KYLIN-2532 at 4/5/17 9:43 AM: -- [~albertoramon] It's a good idea and deserves a try. The hard point is we need to find out all the possible injection points. was (Author: r0ger): [~albertoramon] It's a good idea and deserves a try. The hard point is we need to find out all the possible injection points. > Make Hive flat step more extensible > --- > > Key: KYLIN-2532 > URL: https://issues.apache.org/jira/browse/KYLIN-2532 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Priority: Minor > > How to import data from Hive is defined in Kylin itself. We should make it > more extensible for advanced usage case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2532) Make Hive flat step more extensible
[ https://issues.apache.org/jira/browse/KYLIN-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15956589#comment-15956589 ] Roger Shi commented on KYLIN-2532: -- [~albertoramon] It's a good idea and deserves a try. The hard point is we need to find out all the possible injection points. > Make Hive flat step more extensible > --- > > Key: KYLIN-2532 > URL: https://issues.apache.org/jira/browse/KYLIN-2532 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Priority: Minor > > How to import data from Hive is defined in Kylin itself. We should make it > more extensible for advanced usage case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2532) Make Hive flat step more extensible
Roger Shi created KYLIN-2532: Summary: Make Hive flat step more extensible Key: KYLIN-2532 URL: https://issues.apache.org/jira/browse/KYLIN-2532 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Priority: Minor How to import data from Hive is defined in Kylin itself. We should make it more extensible to advanced usage case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2520) Unify Restful API response and provide versioning
Roger Shi created KYLIN-2520: Summary: Unify Restful API response and provide versioning Key: KYLIN-2520 URL: https://issues.apache.org/jira/browse/KYLIN-2520 Project: Kylin Issue Type: Task Components: REST Service Reporter: Roger Shi Assignee: Zhong,Jason There's no convention in Kylin Restful API's response. It could be an object, an array or just a string. We should refine it in a "New" version Restful API and don't affect the legacy one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KYLIN-2520) Unify Restful API response and provide versioning
[ https://issues.apache.org/jira/browse/KYLIN-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi reassigned KYLIN-2520: Assignee: Roger Shi (was: Zhong,Jason) > Unify Restful API response and provide versioning > - > > Key: KYLIN-2520 > URL: https://issues.apache.org/jira/browse/KYLIN-2520 > Project: Kylin > Issue Type: Task > Components: REST Service >Reporter: Roger Shi >Assignee: Roger Shi > > There's no convention in Kylin Restful API's response. It could be an object, > an array or just a string. We should refine it in a "New" version Restful API > and don't affect the legacy one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-2514) Joins in data model fail to save when they disorder
[ https://issues.apache.org/jira/browse/KYLIN-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2514. -- Resolution: Fixed Assignee: Roger Shi Fix Version/s: v2.0.0 > Joins in data model fail to save when they disorder > --- > > Key: KYLIN-2514 > URL: https://issues.apache.org/jira/browse/KYLIN-2514 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.0.0 >Reporter: Roger Shi >Assignee: Roger Shi > Fix For: v2.0.0 > > > FK table must be declared first and PK table declared later in data model > creation or modification. Otherwise it can't be saved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2514) Joins in data model fail to save when they disorder
[ https://issues.apache.org/jira/browse/KYLIN-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931594#comment-15931594 ] Roger Shi commented on KYLIN-2514: -- Yes. It's expected and is the correct way to organize the join tables. But in the case that user delete one join table in the middle and add a new one in the tail, it usually fails even all the join tables can build a complete join tree. It would be easier for user if backend can accept and reorder the join tables once they can be organized as a join tree. > Joins in data model fail to save when they disorder > --- > > Key: KYLIN-2514 > URL: https://issues.apache.org/jira/browse/KYLIN-2514 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.0.0 >Reporter: Roger Shi > > FK table must be declared first and PK table declared later in data model > creation or modification. Otherwise it can't be saved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2514) Joins in data model fail to save when they disorder
Roger Shi created KYLIN-2514: Summary: Joins in data model fail to save when they disorder Key: KYLIN-2514 URL: https://issues.apache.org/jira/browse/KYLIN-2514 Project: Kylin Issue Type: Bug Affects Versions: v2.0.0 Reporter: Roger Shi FK table must be declared first and PK table declared later in data model creation or modification. Otherwise it can't be saved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-472) Ambari plugin to manage Kylin service
[ https://issues.apache.org/jira/browse/KYLIN-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-472: Labels: bigtask github-import (was: github-import) > Ambari plugin to manage Kylin service > - > > Key: KYLIN-472 > URL: https://issues.apache.org/jira/browse/KYLIN-472 > Project: Kylin > Issue Type: Wish >Reporter: Luke Han >Assignee: Yifan Zhang > Labels: bigtask, github-import > > Ambari is great tool to manage most of Hadoop components in one single place: > ![screen shot 2014-10-30 at 4 08 15 > pm|https://cloud.githubusercontent.com/assets/1104017/4840168/33880466-600c-11e4-8f70-c68e1e6bf353.png] > It make sense to use Ambari to easy manage Kylin serivce in same place. > Requirement: > 1. Deploy and install Kylin service via Ambari > 2. Start and Stop Kylin service through Ambari > 3. Display Kylin service status on Ambari Web > [Call Volunteer!] > -- > We are not Ambari expert, please let's know if you have interesting to > contribute on this! > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/33 > Created by: [lukehan|https://github.com/lukehan] > Labels: > Created at: Thu Oct 30 16:14:46 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-299) Easy config switch according to different deploy env (dev,qa,prod)
[ https://issues.apache.org/jira/browse/KYLIN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-299: Summary: Easy config switch according to different deploy env (dev,qa,prod) (was: add service to differentiate the deploy env) > Easy config switch according to different deploy env (dev,qa,prod) > -- > > Key: KYLIN-299 > URL: https://issues.apache.org/jira/browse/KYLIN-299 > Project: Kylin > Issue Type: Wish > Components: Tools, Build and Test >Reporter: Luke Han >Assignee: Dong Li > Labels: github-import > Fix For: v0.6.5, Future > > > different deploy env (dev,qa,prod) may need different config, > need to add this feature > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/206 > Created by: [janzhongi|https://github.com/janzhongi] > Labels: newfeature, > Assignee: [janzhongi|https://github.com/janzhongi] > Created at: Wed Dec 10 10:46:23 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-299) Easy config switch according to different deploy env
[ https://issues.apache.org/jira/browse/KYLIN-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-299: Summary: Easy config switch according to different deploy env (was: Easy config switch according to different deploy env (dev,qa,prod)) > Easy config switch according to different deploy env > > > Key: KYLIN-299 > URL: https://issues.apache.org/jira/browse/KYLIN-299 > Project: Kylin > Issue Type: Wish > Components: Tools, Build and Test >Reporter: Luke Han >Assignee: Dong Li > Labels: github-import > Fix For: v0.6.5, Future > > > Easy config switch according to different deploy env (dev,qa,prod) > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/206 > Created by: [janzhongi|https://github.com/janzhongi] > Labels: newfeature, > Assignee: [janzhongi|https://github.com/janzhongi] > Created at: Wed Dec 10 10:46:23 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-238) Metadata import / export tool (GUI)
[ https://issues.apache.org/jira/browse/KYLIN-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-238. - Resolution: Fixed Fix Version/s: v1.6.0 http://kylin.apache.org/docs16/howto/howto_backup_metadata.html > Metadata import / export tool (GUI) > --- > > Key: KYLIN-238 > URL: https://issues.apache.org/jira/browse/KYLIN-238 > Project: Kylin > Issue Type: Improvement >Reporter: Luke Han > Labels: github-import > Fix For: v1.6.0 > > > Import and export tool for Kylin relative resources settings > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/267 > Created by: [lukehan|https://github.com/lukehan] > Labels: > Milestone: Backlog > Created at: Fri Dec 26 11:22:09 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-237) Show sample data when clicking Hive table
[ https://issues.apache.org/jira/browse/KYLIN-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-237: Summary: Show sample data when clicking Hive table (was: Sample data of source table) > Show sample data when clicking Hive table > - > > Key: KYLIN-237 > URL: https://issues.apache.org/jira/browse/KYLIN-237 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason >Priority: Minor > Labels: github-import > Fix For: Backlog > > > Display sample data of selected Hive table like 500 records. > User could adjust this number to show more data > Using same pivot grid of query result to bring more capacity for user to > explore source data > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/268 > Created by: [lukehan|https://github.com/lukehan] > Labels: > Milestone: Backlog > Created at: Fri Dec 26 11:23:02 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-235) Support expand via double click on table name
[ https://issues.apache.org/jira/browse/KYLIN-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-235. - Resolution: Fixed Fix Version/s: v1.6.0 Click on the icon or name, table will expand. > Support expand via double click on table name > - > > Key: KYLIN-235 > URL: https://issues.apache.org/jira/browse/KYLIN-235 > Project: Kylin > Issue Type: Wish >Reporter: Luke Han > Labels: github-import > Fix For: v1.6.0 > > > Now, user only have change to expand to click on icon. > It will bring more better experience to support double click on table name. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/270 > Created by: [lukehan|https://github.com/lukehan] > Labels: > Created at: Fri Dec 26 11:25:57 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-231) Regular job to check HBase and HTable's healthy
[ https://issues.apache.org/jira/browse/KYLIN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-231: Labels: github-import newbie (was: github-import) > Regular job to check HBase and HTable's healthy > --- > > Key: KYLIN-231 > URL: https://issues.apache.org/jira/browse/KYLIN-231 > Project: Kylin > Issue Type: Wish > Components: General >Reporter: Luke Han >Assignee: Luke Han >Priority: Trivial > Labels: github-import, newbie > Fix For: Backlog > > > When any issue of backend HBase cluster, it will impact Kylin and customer's > application based on Kylin cube. > Run a regular job to check HBase and HTable's status, alert and notify about > critical issues: > 1. HBase Down > 2. HTable inconsistencies > Any other issues. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/274 > Created by: [lukehan|https://github.com/lukehan] > Labels: > Milestone: Backlog > Created at: Fri Dec 26 13:54:13 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-218) Job Engine Runtime monitoring page
[ https://issues.apache.org/jira/browse/KYLIN-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-218. - Resolution: Fixed It's in monitor page of KYLIN. > Job Engine Runtime monitoring page > -- > > Key: KYLIN-218 > URL: https://issues.apache.org/jira/browse/KYLIN-218 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import > Fix For: Backlog > > > As administrator, I would like to have one admin page to monitoring Job > Engine's runtime performance, queue, jobs, exceptions and so on. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/287 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 14:22:51 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-216) Enable save cube design as draft
[ https://issues.apache.org/jira/browse/KYLIN-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-216: Component/s: Metadata > Enable save cube design as draft > > > Key: KYLIN-216 > URL: https://issues.apache.org/jira/browse/KYLIN-216 > Project: Kylin > Issue Type: Wish > Components: Metadata, Web >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > Cube's metadata will lost when the click other pages or close browser during > their cube creation. This will bring bad experience when they added many > dimensions and measures since they have to start from beginning. > Add "save as draft" feature will enable user to just save draft version and > continue their work later. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/289 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 14:28:16 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-214) Provide accurate column value scope for BI tools
[ https://issues.apache.org/jira/browse/KYLIN-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-214: Summary: Provide accurate column value scope for BI tools (was: Narrow down lookup value scope in project level) > Provide accurate column value scope for BI tools > > > Key: KYLIN-214 > URL: https://issues.apache.org/jira/browse/KYLIN-214 > Project: Kylin > Issue Type: Wish > Components: Query Engine >Reporter: Luke Han >Priority: Minor > Labels: bi, github-import > Fix For: Backlog > > > _Problem: _ > All lookup column's values will show to users, for example, when user move > "dw-cal-dt" to Tableau's quick filter, it will show the date range from 1990 > to 2099 year. This will bring confuse to end users with bad experience. > Solution: > Define lookup scope based on project scope. > Why not based on cube: > Kylin will only expose Hive Tables to users, the engine do not know the > exactly cube when user only query on lookup table. Since user have to choose > project for their query, it make sense to enable such scope filter on project > level. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/291 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 14:30:09 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-214) Narrow down lookup value scope in project level
[ https://issues.apache.org/jira/browse/KYLIN-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-214: Labels: bi github-import (was: github-import) > Narrow down lookup value scope in project level > --- > > Key: KYLIN-214 > URL: https://issues.apache.org/jira/browse/KYLIN-214 > Project: Kylin > Issue Type: Wish > Components: Query Engine >Reporter: Luke Han >Priority: Minor > Labels: bi, github-import > Fix For: Backlog > > > _Problem: _ > All lookup column's values will show to users, for example, when user move > "dw-cal-dt" to Tableau's quick filter, it will show the date range from 1990 > to 2099 year. This will bring confuse to end users with bad experience. > Solution: > Define lookup scope based on project scope. > Why not based on cube: > Kylin will only expose Hive Tables to users, the engine do not know the > exactly cube when user only query on lookup table. Since user have to choose > project for their query, it make sense to enable such scope filter on project > level. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/291 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 14:30:09 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-206) Provide landing page
[ https://issues.apache.org/jira/browse/KYLIN-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-206: Labels: github-import newbie (was: github-import) > Provide landing page > > > Key: KYLIN-206 > URL: https://issues.apache.org/jira/browse/KYLIN-206 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Priority: Trivial > Labels: github-import, newbie > Fix For: Future > > > Sample idea: > ![image|https://cloud.githubusercontent.com/assets/1104017/5556171/87511dc0-8d0d-11e4-9312-f5058f8049c8.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/299 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 14:45:16 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-205) Better Cube Designer Look and Feel
[ https://issues.apache.org/jira/browse/KYLIN-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-205: Summary: Better Cube Designer Look and Feel (was: Cube Designer Look and Feel) > Better Cube Designer Look and Feel > -- > > Key: KYLIN-205 > URL: https://issues.apache.org/jira/browse/KYLIN-205 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han > Labels: github-import, web-enhance > Fix For: Backlog > > Attachments: cube designer.png > > > Sample Idea: > ![image|https://cloud.githubusercontent.com/assets/1104017/5556179/d3aa0da8-8d0d-11e4-9543-d96da0933aca.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/300 > Created by: [lukehan|https://github.com/lukehan] > Labels: enhancement, > Milestone: Backlog > Created at: Fri Dec 26 14:45:55 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-205) Cube Designer Look and Feel
[ https://issues.apache.org/jira/browse/KYLIN-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-205: Labels: github-import web-enhance (was: github-import) > Cube Designer Look and Feel > --- > > Key: KYLIN-205 > URL: https://issues.apache.org/jira/browse/KYLIN-205 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han > Labels: github-import, web-enhance > Fix For: Backlog > > Attachments: cube designer.png > > > Sample Idea: > ![image|https://cloud.githubusercontent.com/assets/1104017/5556179/d3aa0da8-8d0d-11e4-9543-d96da0933aca.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/300 > Created by: [lukehan|https://github.com/lukehan] > Labels: enhancement, > Milestone: Backlog > Created at: Fri Dec 26 14:45:55 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-201) Save as image in visualization result
[ https://issues.apache.org/jira/browse/KYLIN-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-201: Component/s: Web > Save as image in visualization result > - > > Key: KYLIN-201 > URL: https://issues.apache.org/jira/browse/KYLIN-201 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import > Fix For: Backlog > > > As a user, I would like to be able to save visualization as image > The "Export" should perform different approach for Grid and Visualization > view. > ![image|https://cloud.githubusercontent.com/assets/1104017/5556235/af5ddb12-8d0f-11e4-91f9-34bafe13c163.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/304 > Created by: [lukehan|https://github.com/lukehan] > Labels: enhancement, > Created at: Fri Dec 26 14:58:59 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-195) Enable switch fact table in cube metadata
[ https://issues.apache.org/jira/browse/KYLIN-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-195: Labels: github-import metadata (was: github-import) > Enable switch fact table in cube metadata > - > > Key: KYLIN-195 > URL: https://issues.apache.org/jira/browse/KYLIN-195 > Project: Kylin > Issue Type: Wish > Components: Metadata, Web >Reporter: Luke Han >Priority: Minor > Labels: github-import, metadata > Fix For: Backlog > > > As a cube owner, I would like to be able to design my cube with sample fact > table first then build and run to verify in design time, with small data but > same structure to speed up design and troubleshooting. > And when I release it to production, I would like to be able to switch to > production fact table with real data. > Also would like to have this capability be enabled on lookup table. > > This feature should only available when cube could be edit status. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/310 > Created by: [lukehan|https://github.com/lukehan] > Labels: > Milestone: Backlog > Created at: Fri Dec 26 15:06:46 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-193) Show cubes and tables relationship with network visualization
[ https://issues.apache.org/jira/browse/KYLIN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-193: Labels: github-import web-enhance (was: github-import) > Show cubes and tables relationship with network visualization > - > > Key: KYLIN-193 > URL: https://issues.apache.org/jira/browse/KYLIN-193 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Priority: Minor > Labels: github-import, web-enhance > Fix For: Backlog > > > As a user, I would like to know the tables be using in one cube > also would to know all the cubes refereed to one table. > Using network diagram to show this relationship. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/312 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:09:18 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-192) Preview data from SQL when creating/editing Cube
[ https://issues.apache.org/jira/browse/KYLIN-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-192: Labels: github-import web-enhance (was: github-import) > Preview data from SQL when creating/editing Cube > > > Key: KYLIN-192 > URL: https://issues.apache.org/jira/browse/KYLIN-192 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import, web-enhance > Fix For: Future > > > As a cube designer, when I'm creating/editing my cube, I would like to have > ability to preview data which will generate cube for validation/verify and so > on, return limited records is ok, such as 100, 500. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/313 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:11:17 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-192) Preview data from SQL when creating/editing Cube
[ https://issues.apache.org/jira/browse/KYLIN-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-192: Summary: Preview data from SQL when creating/editing Cube (was: Preview data from cube's SQL) > Preview data from SQL when creating/editing Cube > > > Key: KYLIN-192 > URL: https://issues.apache.org/jira/browse/KYLIN-192 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import, web-enhance > Fix For: Future > > > As a cube designer, when I'm creating/editing my cube, I would like to have > ability to preview data which will generate cube for validation/verify and so > on, return limited records is ok, such as 100, 500. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/313 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:11:17 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-190) Visualize Editor for cube creation/edition
[ https://issues.apache.org/jira/browse/KYLIN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-190: Labels: github-import web-enhance (was: github-import) > Visualize Editor for cube creation/edition > -- > > Key: KYLIN-190 > URL: https://issues.apache.org/jira/browse/KYLIN-190 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Luke Han >Priority: Minor > Labels: github-import, web-enhance > Fix For: Backlog > > > Reference: > ![image|https://cloud.githubusercontent.com/assets/1104017/5556285/b79947b0-8d11-11e4-8b4c-84d6edeee5de.png] > ![image|https://cloud.githubusercontent.com/assets/1104017/5556287/bb0e5368-8d11-11e4-8285-cb05b3dcb7f6.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/315 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:13:36 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-191) Unix ODBC Driver
[ https://issues.apache.org/jira/browse/KYLIN-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-191: Labels: github-import gsoc2016 odbc (was: github-import gsoc2016) > Unix ODBC Driver > > > Key: KYLIN-191 > URL: https://issues.apache.org/jira/browse/KYLIN-191 > Project: Kylin > Issue Type: Wish > Components: Driver - ODBC >Reporter: Luke Han >Assignee: Luke Han >Priority: Minor > Labels: github-import, gsoc2016, odbc > Fix For: Backlog > > > To support more BI platform and tools, the unix ODBC driver version is > required to be enabled on the Linux/Unix based application and platform which > consume Kylin through ODBC protocol > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/314 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:12:11 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-187) Data Statistics Collection and Auto Modeling
[ https://issues.apache.org/jira/browse/KYLIN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-187: Summary: Data Statistics Collection and Auto Modeling (was: Data Statistics Analyzer ) > Data Statistics Collection and Auto Modeling > - > > Key: KYLIN-187 > URL: https://issues.apache.org/jira/browse/KYLIN-187 > Project: Kylin > Issue Type: New Feature > Components: Tools, Build and Test >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > 1 Overview > We need the statistics data for the following domains: > * Design cube metadata based on query log > * Design HBase row-key based on data distribution (e.g. histogram and > cardinality) > * Choose execution plan based on cuboid data > 2 Data Analyzer > We need to analyzer the hive data and cube data in 2 phases. Firstly, we will > analyze the hive to guide the 1st round design of row key. Then we will > analyze the cube data to refine the design of row key and to estimate the > cost of query. > 2.1 Analyze Hive Data > We need to analyze the following statistics data on hive table: > * Cardinality of each dimension > * Cardinality of dimension combination (optional) > * Value distribution of each dimension (optional) > Based on the statistics of hive data, we can design row key group from high > cardinality dimension to low cardinality dimension. BTW, we should evenly > split dimension into the row key group that will reduce the number of cuboid. > 2.2 Analyze Cube Data > We need to analyze the following statistics on data cube: > * Count of each cuboid > * Group ratio of each cuboid = current cuboid count / lower group base cuboid > count > 3 Query Analyzer > TBD > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/318 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:21:24 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-185) Display Hadoop System Components Status
[ https://issues.apache.org/jira/browse/KYLIN-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-185: Summary: Display Hadoop System Components Status (was: Display Hadoo System Components Status) > Display Hadoop System Components Status > --- > > Key: KYLIN-185 > URL: https://issues.apache.org/jira/browse/KYLIN-185 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > As an administrator, I would like to have one single view to know all > dependency's status, including: > 1. HDFS > 2. Hive > 3. HBase > 4. ZooKeeper > 5. MySQL > 6. Kerberos > 7. LDAP > 8. Others. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/320 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:22:53 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-183) Execute and Display SQL Explain in query page
[ https://issues.apache.org/jira/browse/KYLIN-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-183: Labels: github-import web-enhance (was: github-import) > Execute and Display SQL Explain in query page > - > > Key: KYLIN-183 > URL: https://issues.apache.org/jira/browse/KYLIN-183 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import, web-enhance > Fix For: Backlog > > > As a user, I would like to: > 1. Execute SQL Explain Plan before execute real SQL > 2. Display SQL Explain Plan with user information, such as how many rows will > be scan, how many rows will be returned, and the each step's cost (if have) > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/322 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: v2.0 Release > Created at: Fri Dec 26 15:24:49 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-189) ODBC prepared statement
[ https://issues.apache.org/jira/browse/KYLIN-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-189: Labels: github-import odbc (was: github-import) > ODBC prepared statement > --- > > Key: KYLIN-189 > URL: https://issues.apache.org/jira/browse/KYLIN-189 > Project: Kylin > Issue Type: Improvement > Components: Driver - ODBC >Reporter: Luke Han >Assignee: hongbin ma > Labels: github-import, odbc > Fix For: Backlog > > > Support ODBC prepared statement > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/316 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:15:36 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-181) Enhance filter on high cardinality in Tableau
[ https://issues.apache.org/jira/browse/KYLIN-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-181: Labels: bi github-import (was: github-import) > Enhance filter on high cardinality in Tableau > - > > Key: KYLIN-181 > URL: https://issues.apache.org/jira/browse/KYLIN-181 > Project: Kylin > Issue Type: Wish >Reporter: Luke Han > Labels: bi, github-import > Fix For: Future > > > When user use seller_id as filter, the current ODBC will only show the first > 100K scan result. And the query will not re-run when given specific value. > There's enhancement should be offered from Tableau side to aware such high > cardinality column and perform different behavior to avoid such issue. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/325 > Created by: [lukehan|https://github.com/lukehan] > Labels: enhancement, > Milestone: Backlog > Created at: Fri Dec 26 15:32:09 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-187) Data Statistics Analyzer
[ https://issues.apache.org/jira/browse/KYLIN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-187: Description: 1 Overview We need the statistics data for the following domains: * Design cube metadata based on query log * Design HBase row-key based on data distribution (e.g. histogram and cardinality) * Choose execution plan based on cuboid data 2 Data Analyzer We need to analyzer the hive data and cube data in 2 phases. Firstly, we will analyze the hive to guide the 1st round design of row key. Then we will analyze the cube data to refine the design of row key and to estimate the cost of query. 2.1 Analyze Hive Data We need to analyze the following statistics data on hive table: * Cardinality of each dimension * Cardinality of dimension combination (optional) * Value distribution of each dimension (optional) Based on the statistics of hive data, we can design row key group from high cardinality dimension to low cardinality dimension. BTW, we should evenly split dimension into the row key group that will reduce the number of cuboid. 2.2 Analyze Cube Data We need to analyze the following statistics on data cube: * Count of each cuboid * Group ratio of each cuboid = current cuboid count / lower group base cuboid count 3 Query Analyzer TBD Imported from GitHub Url: https://github.com/KylinOLAP/Kylin/issues/318 Created by: [lukehan|https://github.com/lukehan] Labels: newfeature, Milestone: Backlog Created at: Fri Dec 26 15:21:24 CST 2014 State: open was: # Overview We need the statistics data for the following domains: * Design cube metadata based on query log * Design HBase row-key based on data distribution (e.g. histogram and cardinality) * Choose execution plan based on cuboid data # Data Analyzer We need to analyzer the hive data and cube data in 2 phases. Firstly, we will analyze the hive to guide the 1st round design of row key. Then we will analyze the cube data to refine the design of row key and to estimate the cost of query. ## Analyze Hive Data We need to analyze the following statistics data on hive table: * Cardinality of each dimension * Cardinality of dimension combination (optional) * Value distribution of each dimension (optional) Based on the statistics of hive data, we can design row key group from high cardinality dimension to low cardinality dimension. BTW, we should evenly split dimension into the row key group that will reduce the number of cuboid. ## Analyze Cube Data We need to analyze the following statistics on data cube: * Count of each cuboid * Group ratio of each cuboid = current cuboid count / lower group base cuboid count # Query Analyzer TBD Imported from GitHub Url: https://github.com/KylinOLAP/Kylin/issues/318 Created by: [lukehan|https://github.com/lukehan] Labels: newfeature, Milestone: Backlog Created at: Fri Dec 26 15:21:24 CST 2014 State: open > Data Statistics Analyzer > - > > Key: KYLIN-187 > URL: https://issues.apache.org/jira/browse/KYLIN-187 > Project: Kylin > Issue Type: New Feature > Components: Tools, Build and Test >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > 1 Overview > We need the statistics data for the following domains: > * Design cube metadata based on query log > * Design HBase row-key based on data distribution (e.g. histogram and > cardinality) > * Choose execution plan based on cuboid data > 2 Data Analyzer > We need to analyzer the hive data and cube data in 2 phases. Firstly, we will > analyze the hive to guide the 1st round design of row key. Then we will > analyze the cube data to refine the design of row key and to estimate the > cost of query. > 2.1 Analyze Hive Data > We need to analyze the following statistics data on hive table: > * Cardinality of each dimension > * Cardinality of dimension combination (optional) > * Value distribution of each dimension (optional) > Based on the statistics of hive data, we can design row key group from high > cardinality dimension to low cardinality dimension. BTW, we should evenly > split dimension into the row key group that will reduce the number of cuboid. > 2.2 Analyze Cube Data > We need to analyze the following statistics on data cube: > * Count of each cuboid > * Group ratio of each cuboid = current cuboid count / lower group base cuboid > count > 3 Query Analyzer > TBD > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/318 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:21:24 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-187) Data Statistics Analyzer
[ https://issues.apache.org/jira/browse/KYLIN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-187: Description: # Overview We need the statistics data for the following domains: * Design cube metadata based on query log * Design HBase row-key based on data distribution (e.g. histogram and cardinality) * Choose execution plan based on cuboid data # Data Analyzer We need to analyzer the hive data and cube data in 2 phases. Firstly, we will analyze the hive to guide the 1st round design of row key. Then we will analyze the cube data to refine the design of row key and to estimate the cost of query. ## Analyze Hive Data We need to analyze the following statistics data on hive table: * Cardinality of each dimension * Cardinality of dimension combination (optional) * Value distribution of each dimension (optional) Based on the statistics of hive data, we can design row key group from high cardinality dimension to low cardinality dimension. BTW, we should evenly split dimension into the row key group that will reduce the number of cuboid. ## Analyze Cube Data We need to analyze the following statistics on data cube: * Count of each cuboid * Group ratio of each cuboid = current cuboid count / lower group base cuboid count # Query Analyzer TBD Imported from GitHub Url: https://github.com/KylinOLAP/Kylin/issues/318 Created by: [lukehan|https://github.com/lukehan] Labels: newfeature, Milestone: Backlog Created at: Fri Dec 26 15:21:24 CST 2014 State: open was: ## 1. Overview We need the statistics data for the following domains: * Design cube metadata based on query log * Design HBase row-key based on data distribution (e.g. histogram and cardinality) * Choose execution plan based on cuboid data ## 2. Data Analyzer We need to analyzer the hive data and cube data in 2 phases. Firstly, we will analyze the hive to guide the 1st round design of row key. Then we will analyze the cube data to refine the design of row key and to estimate the cost of query. 2.1. Analyze Hive Data We need to analyze the following statistics data on hive table: * Cardinality of each dimension * Cardinality of dimension combination (optional) * Value distribution of each dimension (optional) Based on the statistics of hive data, we can design row key group from high cardinality dimension to low cardinality dimension. BTW, we should evenly split dimension into the row key group that will reduce the number of cuboid. 2.2. Analyze Cube Data We need to analyze the following statistics on data cube: * Count of each cuboid * Group ratio of each cuboid = current cuboid count / lower group base cuboid count 3. Query Analyzer TBD Imported from GitHub Url: https://github.com/KylinOLAP/Kylin/issues/318 Created by: [lukehan|https://github.com/lukehan] Labels: newfeature, Milestone: Backlog Created at: Fri Dec 26 15:21:24 CST 2014 State: open > Data Statistics Analyzer > - > > Key: KYLIN-187 > URL: https://issues.apache.org/jira/browse/KYLIN-187 > Project: Kylin > Issue Type: New Feature > Components: Tools, Build and Test >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > # Overview > We need the statistics data for the following domains: > * Design cube metadata based on query log > * Design HBase row-key based on data distribution (e.g. histogram and > cardinality) > * Choose execution plan based on cuboid data > # Data Analyzer > We need to analyzer the hive data and cube data in 2 phases. Firstly, we will > analyze the hive to guide the 1st round design of row key. Then we will > analyze the cube data to refine the design of row key and to estimate the > cost of query. > ## Analyze Hive Data > We need to analyze the following statistics data on hive table: > * Cardinality of each dimension > * Cardinality of dimension combination (optional) > * Value distribution of each dimension (optional) > Based on the statistics of hive data, we can design row key group from high > cardinality dimension to low cardinality dimension. BTW, we should evenly > split dimension into the row key group that will reduce the number of cuboid. > ## Analyze Cube Data > We need to analyze the following statistics on data cube: > * Count of each cuboid > * Group ratio of each cuboid = current cuboid count / lower group base cuboid > count > # Query Analyzer > TBD > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/318 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:21:24 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-187) Data Statistics Analyzer
[ https://issues.apache.org/jira/browse/KYLIN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-187: Request participants: (was: ) Description: #Overview We need the statistics data for the following domains: * Design cube metadata based on query log * Design HBase row-key based on data distribution (e.g. histogram and cardinality) * Choose execution plan based on cuboid data #Data Analyzer We need to analyzer the hive data and cube data in 2 phases. Firstly, we will analyze the hive to guide the 1st round design of row key. Then we will analyze the cube data to refine the design of row key and to estimate the cost of query. ##Analyze Hive Data We need to analyze the following statistics data on hive table: * Cardinality of each dimension * Cardinality of dimension combination (optional) * Value distribution of each dimension (optional) Based on the statistics of hive data, we can design row key group from high cardinality dimension to low cardinality dimension. BTW, we should evenly split dimension into the row key group that will reduce the number of cuboid. ##Analyze Cube Data We need to analyze the following statistics on data cube: * Count of each cuboid * Group ratio of each cuboid = current cuboid count / lower group base cuboid count # Query Analyzer TBD Imported from GitHub Url: https://github.com/KylinOLAP/Kylin/issues/318 Created by: [lukehan|https://github.com/lukehan] Labels: newfeature, Milestone: Backlog Created at: Fri Dec 26 15:21:24 CST 2014 State: open was: ## 1. Overview We need the statistics data for the following domains: * Design cube metadata based on query log * Design HBase row-key based on data distribution (e.g. histogram and cardinality) * Choose execution plan based on cuboid data ## 2. Data Analyzer We need to analyzer the hive data and cube data in 2 phases. Firstly, we will analyze the hive to guide the 1st round design of row key. Then we will analyze the cube data to refine the design of row key and to estimate the cost of query. 2.1. Analyze Hive Data We need to analyze the following statistics data on hive table: * Cardinality of each dimension * Cardinality of dimension combination (optional) * Value distribution of each dimension (optional) Based on the statistics of hive data, we can design row key group from high cardinality dimension to low cardinality dimension. BTW, we should evenly split dimension into the row key group that will reduce the number of cuboid. 2.2. Analyze Cube Data We need to analyze the following statistics on data cube: * Count of each cuboid * Group ratio of each cuboid = current cuboid count / lower group base cuboid count 3. Query Analyzer TBD Imported from GitHub Url: https://github.com/KylinOLAP/Kylin/issues/318 Created by: [lukehan|https://github.com/lukehan] Labels: newfeature, Milestone: Backlog Created at: Fri Dec 26 15:21:24 CST 2014 State: open > Data Statistics Analyzer > - > > Key: KYLIN-187 > URL: https://issues.apache.org/jira/browse/KYLIN-187 > Project: Kylin > Issue Type: New Feature > Components: Tools, Build and Test >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > #Overview > We need the statistics data for the following domains: > * Design cube metadata based on query log > * Design HBase row-key based on data distribution (e.g. histogram and > cardinality) > * Choose execution plan based on cuboid data > #Data Analyzer > We need to analyzer the hive data and cube data in 2 phases. Firstly, we will > analyze the hive to guide the 1st round design of row key. Then we will > analyze the cube data to refine the design of row key and to estimate the > cost of query. > ##Analyze Hive Data > We need to analyze the following statistics data on hive table: > * Cardinality of each dimension > * Cardinality of dimension combination (optional) > * Value distribution of each dimension (optional) > Based on the statistics of hive data, we can design row key group from high > cardinality dimension to low cardinality dimension. BTW, we should evenly > split dimension into the row key group that will reduce the number of cuboid. > ##Analyze Cube Data > We need to analyze the following statistics on data cube: > * Count of each cuboid > * Group ratio of each cuboid = current cuboid count / lower group base cuboid > count > # Query Analyzer > TBD > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/318 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:21:24 CST 2014 > State: open -- This message was sent by Atlassian JIRA
[jira] [Updated] (KYLIN-187) Data Statistics Analyzer
[ https://issues.apache.org/jira/browse/KYLIN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-187: Description: ## 1. Overview We need the statistics data for the following domains: * Design cube metadata based on query log * Design HBase row-key based on data distribution (e.g. histogram and cardinality) * Choose execution plan based on cuboid data ## 2. Data Analyzer We need to analyzer the hive data and cube data in 2 phases. Firstly, we will analyze the hive to guide the 1st round design of row key. Then we will analyze the cube data to refine the design of row key and to estimate the cost of query. 2.1. Analyze Hive Data We need to analyze the following statistics data on hive table: * Cardinality of each dimension * Cardinality of dimension combination (optional) * Value distribution of each dimension (optional) Based on the statistics of hive data, we can design row key group from high cardinality dimension to low cardinality dimension. BTW, we should evenly split dimension into the row key group that will reduce the number of cuboid. 2.2. Analyze Cube Data We need to analyze the following statistics on data cube: * Count of each cuboid * Group ratio of each cuboid = current cuboid count / lower group base cuboid count 3. Query Analyzer TBD Imported from GitHub Url: https://github.com/KylinOLAP/Kylin/issues/318 Created by: [lukehan|https://github.com/lukehan] Labels: newfeature, Milestone: Backlog Created at: Fri Dec 26 15:21:24 CST 2014 State: open was: #Overview We need the statistics data for the following domains: * Design cube metadata based on query log * Design HBase row-key based on data distribution (e.g. histogram and cardinality) * Choose execution plan based on cuboid data #Data Analyzer We need to analyzer the hive data and cube data in 2 phases. Firstly, we will analyze the hive to guide the 1st round design of row key. Then we will analyze the cube data to refine the design of row key and to estimate the cost of query. ##Analyze Hive Data We need to analyze the following statistics data on hive table: * Cardinality of each dimension * Cardinality of dimension combination (optional) * Value distribution of each dimension (optional) Based on the statistics of hive data, we can design row key group from high cardinality dimension to low cardinality dimension. BTW, we should evenly split dimension into the row key group that will reduce the number of cuboid. ##Analyze Cube Data We need to analyze the following statistics on data cube: * Count of each cuboid * Group ratio of each cuboid = current cuboid count / lower group base cuboid count # Query Analyzer TBD Imported from GitHub Url: https://github.com/KylinOLAP/Kylin/issues/318 Created by: [lukehan|https://github.com/lukehan] Labels: newfeature, Milestone: Backlog Created at: Fri Dec 26 15:21:24 CST 2014 State: open > Data Statistics Analyzer > - > > Key: KYLIN-187 > URL: https://issues.apache.org/jira/browse/KYLIN-187 > Project: Kylin > Issue Type: New Feature > Components: Tools, Build and Test >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > ## 1. Overview > We need the statistics data for the following domains: > * Design cube metadata based on query log > * Design HBase row-key based on data distribution (e.g. histogram and > cardinality) > * Choose execution plan based on cuboid data > ## 2. Data Analyzer > We need to analyzer the hive data and cube data in 2 phases. Firstly, we will > analyze the hive to guide the 1st round design of row key. Then we will > analyze the cube data to refine the design of row key and to estimate the > cost of query. > 2.1. Analyze Hive Data > We need to analyze the following statistics data on hive table: > * Cardinality of each dimension > * Cardinality of dimension combination (optional) > * Value distribution of each dimension (optional) > Based on the statistics of hive data, we can design row key group from high > cardinality dimension to low cardinality dimension. BTW, we should evenly > split dimension into the row key group that will reduce the number of cuboid. > 2.2. Analyze Cube Data > We need to analyze the following statistics on data cube: > * Count of each cuboid > * Group ratio of each cuboid = current cuboid count / lower group base cuboid > count > 3. Query Analyzer > TBD > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/318 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:21:24 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (KYLIN-186) System Health Indictor for end user
[ https://issues.apache.org/jira/browse/KYLIN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi closed KYLIN-186. --- Resolution: Duplicate > System Health Indictor for end user > --- > > Key: KYLIN-186 > URL: https://issues.apache.org/jira/browse/KYLIN-186 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Kejia Wang >Priority: Trivial > Labels: github-import > Fix For: Backlog > > > As an end user, I would like to know is the entire system available or with > any issue, and what's kind of the root cause: Hadoop Cluster? Map Reduce Job > and so on. > Also I would like to have a more detail view of each status. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/319 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:22:18 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-188) REST server expose metrics for job engine & query engine
[ https://issues.apache.org/jira/browse/KYLIN-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-188: Labels: bigtask github-import (was: github-import) > REST server expose metrics for job engine & query engine > > > Key: KYLIN-188 > URL: https://issues.apache.org/jira/browse/KYLIN-188 > Project: Kylin > Issue Type: Wish > Components: REST Service >Reporter: Luke Han >Priority: Minor > Labels: bigtask, github-import > Fix For: Backlog > > > 1. Rest server need to expose the metrics for job engine & query engine > 2. Job Engine expose metrics for job: job queue length, job latency, job > count ... > 3. Query engine expose metrics for query: query latency, query scan count, > qps ... > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/317 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:16:53 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KYLIN-2420) Record zookeeper lock holder information
[ https://issues.apache.org/jira/browse/KYLIN-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2420. -- Resolution: Fixed > Record zookeeper lock holder information > > > Key: KYLIN-2420 > URL: https://issues.apache.org/jira/browse/KYLIN-2420 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Priority: Minor > Attachments: > 0001-KYLIN-2420-Record-zookeeper-lock-holder-information.patch > > > Kylin should record zookeeper lock holder information such as process id and > host name. If one instance can't acquire a lock, at least we know which one > is holding it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2420) Record zookeeper lock holder information
[ https://issues.apache.org/jira/browse/KYLIN-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-2420: - Attachment: 0001-KYLIN-2420-Record-zookeeper-lock-holder-information.patch > Record zookeeper lock holder information > > > Key: KYLIN-2420 > URL: https://issues.apache.org/jira/browse/KYLIN-2420 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Priority: Minor > Attachments: > 0001-KYLIN-2420-Record-zookeeper-lock-holder-information.patch > > > Kylin should record zookeeper lock holder information such as process id and > host name. If one instance can't acquire a lock, at least we know which one > is holding it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KYLIN-2420) Record zookeeper lock holder information
Roger Shi created KYLIN-2420: Summary: Record zookeeper lock holder information Key: KYLIN-2420 URL: https://issues.apache.org/jira/browse/KYLIN-2420 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Priority: Minor Kylin should record zookeeper lock holder information such as process id and host name. If one instance can't acquire a lock, at least we know which one is holding it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2191) Integer encoding error for width from 5 to 7
[ https://issues.apache.org/jira/browse/KYLIN-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-2191: - Attachment: ab6e083517a16bece87db34d9f7f22a5df0662ee.patch > Integer encoding error for width from 5 to 7 > > > Key: KYLIN-2191 > URL: https://issues.apache.org/jira/browse/KYLIN-2191 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.5.4, v1.5.4.1 >Reporter: Roger Shi >Assignee: Roger Shi > Fix For: v1.6.1 > > Attachments: ab6e083517a16bece87db34d9f7f22a5df0662ee.patch > > > For integer encoding, if width is 5, 6 and 7. The decoded value is not right. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2191) Integer encoding error for width from 5 to 7
[ https://issues.apache.org/jira/browse/KYLIN-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2191. -- Resolution: Fixed > Integer encoding error for width from 5 to 7 > > > Key: KYLIN-2191 > URL: https://issues.apache.org/jira/browse/KYLIN-2191 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.5.4, v1.5.4.1 >Reporter: Roger Shi >Assignee: Roger Shi > Fix For: v1.6.1 > > Attachments: ab6e083517a16bece87db34d9f7f22a5df0662ee.patch > > > For integer encoding, if width is 5, 6 and 7. The decoded value is not right. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2197) Has only base cuboid for some cube desc
[ https://issues.apache.org/jira/browse/KYLIN-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2197. -- Resolution: Fixed > Has only base cuboid for some cube desc > --- > > Key: KYLIN-2197 > URL: https://issues.apache.org/jira/browse/KYLIN-2197 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: Roger Shi > Attachments: f3d19f6da20fa415eac641b8daf6081b3eaaf9d4.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2201) Cube desc and aggregation group rule combination max check fail
[ https://issues.apache.org/jira/browse/KYLIN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-2201: - Attachment: 297730dc97e705f2c8526dcdc7718cee900e40e9.patch 00ba74327a0322e1ce62d3c1cf7953ab21ae9407.patch > Cube desc and aggregation group rule combination max check fail > --- > > Key: KYLIN-2201 > URL: https://issues.apache.org/jira/browse/KYLIN-2201 > Project: Kylin > Issue Type: Bug >Reporter: Roger Shi > Attachments: 00ba74327a0322e1ce62d3c1cf7953ab21ae9407.patch, > 297730dc97e705f2c8526dcdc7718cee900e40e9.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2201) Cube desc and aggregation group rule combination max check fail
[ https://issues.apache.org/jira/browse/KYLIN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2201. -- Resolution: Fixed > Cube desc and aggregation group rule combination max check fail > --- > > Key: KYLIN-2201 > URL: https://issues.apache.org/jira/browse/KYLIN-2201 > Project: Kylin > Issue Type: Bug >Reporter: Roger Shi > Attachments: 00ba74327a0322e1ce62d3c1cf7953ab21ae9407.patch, > 297730dc97e705f2c8526dcdc7718cee900e40e9.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2197) Has only base cuboid for some cube desc
[ https://issues.apache.org/jira/browse/KYLIN-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-2197: - Attachment: f3d19f6da20fa415eac641b8daf6081b3eaaf9d4.patch > Has only base cuboid for some cube desc > --- > > Key: KYLIN-2197 > URL: https://issues.apache.org/jira/browse/KYLIN-2197 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: Roger Shi > Attachments: f3d19f6da20fa415eac641b8daf6081b3eaaf9d4.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2201) Cube desc and aggregation group rule combination max check fail
Roger Shi created KYLIN-2201: Summary: Cube desc and aggregation group rule combination max check fail Key: KYLIN-2201 URL: https://issues.apache.org/jira/browse/KYLIN-2201 Project: Kylin Issue Type: Bug Reporter: Roger Shi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2191) Integer encoding error for width from 5 to 7
[ https://issues.apache.org/jira/browse/KYLIN-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-2191: - Summary: Integer encoding error for width from 5 to 7 (was: Integer encoding error for width from 3 to 7) > Integer encoding error for width from 5 to 7 > > > Key: KYLIN-2191 > URL: https://issues.apache.org/jira/browse/KYLIN-2191 > Project: Kylin > Issue Type: Bug >Reporter: Roger Shi >Assignee: Roger Shi > > For integer encoding, if width is 3, 4, 5, 6 and 7. The decoded value is not > right. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2191) Integer encoding error for width from 3 to 7
Roger Shi created KYLIN-2191: Summary: Integer encoding error for width from 3 to 7 Key: KYLIN-2191 URL: https://issues.apache.org/jira/browse/KYLIN-2191 Project: Kylin Issue Type: Bug Reporter: Roger Shi Assignee: Roger Shi For integer encoding, if width is 3, 4, 5, 6 and 7. The decoded value is not right. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2164) Cube metadata broken error message missing
Roger Shi created KYLIN-2164: Summary: Cube metadata broken error message missing Key: KYLIN-2164 URL: https://issues.apache.org/jira/browse/KYLIN-2164 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Assignee: Roger Shi Priority: Minor Once the cube's metadata gets broken, the Web UI shows its state as BROKEN, while there's no detailed error even in log. We should print the detailed log in kylin.log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2139) record Hive intermediate table size
[ https://issues.apache.org/jira/browse/KYLIN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2139. -- Resolution: Invalid > record Hive intermediate table size > --- > > Key: KYLIN-2139 > URL: https://issues.apache.org/jira/browse/KYLIN-2139 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Assignee: Roger Shi >Priority: Minor > > kylin only record Hive intermediate table row count, sometimes its size is > also required. Record it for later reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2139) record Hive intermediate table size
[ https://issues.apache.org/jira/browse/KYLIN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-2139: - Priority: Minor (was: Major) > record Hive intermediate table size > --- > > Key: KYLIN-2139 > URL: https://issues.apache.org/jira/browse/KYLIN-2139 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi >Assignee: Roger Shi >Priority: Minor > > kylin only record Hive intermediate table row count, sometimes its size is > also required. Record it for later reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2139) record Hive intermediate table size
Roger Shi created KYLIN-2139: Summary: record Hive intermediate table size Key: KYLIN-2139 URL: https://issues.apache.org/jira/browse/KYLIN-2139 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Assignee: Roger Shi kylin only record Hive intermediate table row count, sometimes its size is also required. Record it for later reference. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KYLIN-2028) find-*-dependency script fail on Mac OS
[ https://issues.apache.org/jira/browse/KYLIN-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi reassigned KYLIN-2028: Assignee: Roger Shi > find-*-dependency script fail on Mac OS > --- > > Key: KYLIN-2028 > URL: https://issues.apache.org/jira/browse/KYLIN-2028 > Project: Kylin > Issue Type: Bug >Reporter: Roger Shi >Assignee: Roger Shi >Priority: Minor > > command "cut" doesn't support "--output-delimiter" on Mac -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2028) find-*-dependency script fail on Mac OS
Roger Shi created KYLIN-2028: Summary: find-*-dependency script fail on Mac OS Key: KYLIN-2028 URL: https://issues.apache.org/jira/browse/KYLIN-2028 Project: Kylin Issue Type: Bug Reporter: Roger Shi Priority: Minor command "cut" doesn't support "--output-delimiter" on Mac -- This message was sent by Atlassian JIRA (v6.3.4#6332)
