[jira] [Commented] (KYLIN-3351) Cube Planner not working in apche kylin 2.3.0(open Source)
[ https://issues.apache.org/jira/browse/KYLIN-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466756#comment-16466756 ] Lisa Li commented on KYLIN-3351: [~praveenece], did you build the System cube by the cron job regularly? [http://kylin.apache.org/docs23/howto/howto_setup_systemcube.html] > Cube Planner not working in apche kylin 2.3.0(open Source) > -- > > Key: KYLIN-3351 > URL: https://issues.apache.org/jira/browse/KYLIN-3351 > Project: Kylin > Issue Type: Task >Reporter: praveenece >Priority: Major > > Hi Team > i want test Cube planner in apache-kylin(2.3.0),So i created cube with > segment, and i hit query to cube many times more than thousands but the cube > planner there is no change in cuboid level like color changing and not get > COUNT in exactly row count and other items.can u please guide me. > Note: > Could u tell me? > Cube Planner Working only old Cube (like 3 month before) or new Cube also. > Configuration(kylin.Properties) > kylin.cube.cubeplanner.enabled=true > Kylin Version=2.3.0(SINGLE NODE) > MyCube creation =10days before > I referred: http://kylin.apache.org/docs23/howto/howto_use_cube_planner.html > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (KYLIN-3359) Support sum(expression) if possible
[
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466008#comment-16466008
]
Zhong Yanghong edited comment on KYLIN-3359 at 5/7/18 3:18 PM:
---
The patch will change coprocessor related code. However, it's backward
compatible.
With latest code & coprocessor, the following sample query will be supported.
{code:java}
select LSTG_FORMAT_NAME,
sum(price),
sum(case
when LSTG_FORMAT_NAME = 'ABIN' then 2*price
when LSTG_FORMAT_NAME = 'Auction' then
(1+2)*price*(2+3)+(2+3)*(3+2)*(4+5)-4+5
else 3
end)
FROM test_kylin_fact
inner JOIN edw.test_cal_dt as test_cal_dt
ON test_kylin_fact.cal_dt = test_cal_dt.cal_dt
inner JOIN test_category_groupings
ON test_kylin_fact.leaf_categ_id = test_category_groupings.leaf_categ_id
AND test_kylin_fact.lstg_site_id = test_category_groupings.site_id
WHERE SLR_SEGMENT_CD < 16
group by LSTG_FORMAT_NAME
having sum((1+2)*price*(2+3)+(2+3)*(3+2)*(4+5)-4+5) > 180
order by LSTG_FORMAT_NAME
{code}
was (Author: yaho):
The patch will change coprocessor related code. However, it's backward
compatible.
After deploy latest coprocessor, the following sample query will be supported.
{code}
select LSTG_FORMAT_NAME,
sum(price),
sum(case
when LSTG_FORMAT_NAME = 'ABIN' then 2*price
when LSTG_FORMAT_NAME = 'Auction' then
(1+2)*price*(2+3)+(2+3)*(3+2)*(4+5)-4+5
else 3
end)
FROM test_kylin_fact
inner JOIN edw.test_cal_dt as test_cal_dt
ON test_kylin_fact.cal_dt = test_cal_dt.cal_dt
inner JOIN test_category_groupings
ON test_kylin_fact.leaf_categ_id = test_category_groupings.leaf_categ_id
AND test_kylin_fact.lstg_site_id = test_category_groupings.site_id
WHERE SLR_SEGMENT_CD < 16
group by LSTG_FORMAT_NAME
having sum((1+2)*price*(2+3)+(2+3)*(3+2)*(4+5)-4+5) > 180
order by LSTG_FORMAT_NAME
{code}
> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
> Issue Type: Sub-task
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> The expression can be as follows:
> # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
> # case when {{filter}} ~1~ then expr ~1~
> when {{filter}} ~2~ then expr ~2~
> ...
> else expr ~N~
> end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr
> ~1~,expr ~2~,...expr ~N~ are supported
> There's a constraint for the filter. That is it's able to push down the
> related filters in case when.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3359) Support sum(expression) if possible
[
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466008#comment-16466008
]
Zhong Yanghong commented on KYLIN-3359:
---
The patch will change coprocessor related code. However, it's backward
compatible.
After deploy latest coprocessor, the following sample query will be supported.
{code}
select LSTG_FORMAT_NAME,
sum(price),
sum(case
when LSTG_FORMAT_NAME = 'ABIN' then 2*price
when LSTG_FORMAT_NAME = 'Auction' then
(1+2)*price*(2+3)+(2+3)*(3+2)*(4+5)-4+5
else 3
end)
FROM test_kylin_fact
inner JOIN edw.test_cal_dt as test_cal_dt
ON test_kylin_fact.cal_dt = test_cal_dt.cal_dt
inner JOIN test_category_groupings
ON test_kylin_fact.leaf_categ_id = test_category_groupings.leaf_categ_id
AND test_kylin_fact.lstg_site_id = test_category_groupings.site_id
WHERE SLR_SEGMENT_CD < 16
group by LSTG_FORMAT_NAME
having sum((1+2)*price*(2+3)+(2+3)*(3+2)*(4+5)-4+5) > 180
order by LSTG_FORMAT_NAME
{code}
> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
> Issue Type: Sub-task
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> The expression can be as follows:
> # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
> # case when {{filter}} ~1~ then expr ~1~
> when {{filter}} ~2~ then expr ~2~
> ...
> else expr ~N~
> end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr
> ~1~,expr ~2~,...expr ~N~ are supported
> There's a constraint for the filter. That is it's able to push down the
> related filters in case when.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3359) Support sum(expression) if possible
[
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16466006#comment-16466006
]
Zhong Yanghong commented on KYLIN-3359:
---
https://github.com/apache/kylin/pull/138
> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
> Issue Type: Sub-task
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> The expression can be as follows:
> # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
> # case when {{filter}} ~1~ then expr ~1~
> when {{filter}} ~2~ then expr ~2~
> ...
> else expr ~N~
> end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr
> ~1~,expr ~2~,...expr ~N~ are supported
> There's a constraint for the filter. That is it's able to push down the
> related filters in case when.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3071) Add config to reuse dict to reduce dict size
[ https://issues.apache.org/jira/browse/KYLIN-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465781#comment-16465781 ] Shaofeng SHI commented on KYLIN-3071: - [~liyang.g...@gmail.com] Growing Dict will base on the biggest dict to build a new dictionary (when there is new value not covered). The drawback is, a small segment may uses a very big dictionary. Hao's change is, if there is an existing dictionary contains all the values, then use it. It won't make the dictionary bigger. > Add config to reuse dict to reduce dict size > - > > Key: KYLIN-3071 > URL: https://issues.apache.org/jira/browse/KYLIN-3071 > Project: Kylin > Issue Type: Improvement > Components: Metadata >Reporter: Yang Hao >Assignee: Yang Hao >Priority: Major > Fix For: Future > > Attachments: KYLIN-3071.apache-master.001.patch > > > When calling DictionaryManager.trySaveNewDict, and growing dict is not > enabled, it only use the history dict which is equal, it may generate many > dict. We should supply a config to use contains instead of equal to reuse old > dict. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3071) Add config to reuse dict to reduce dict size
[
https://issues.apache.org/jira/browse/KYLIN-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465584#comment-16465584
]
liyang commented on KYLIN-3071:
---
How is this different from {{KylinConfigBase.isGrowingDictEnabled()}} ?
> Add config to reuse dict to reduce dict size
> -
>
> Key: KYLIN-3071
> URL: https://issues.apache.org/jira/browse/KYLIN-3071
> Project: Kylin
> Issue Type: Improvement
> Components: Metadata
>Reporter: Yang Hao
>Assignee: Yang Hao
>Priority: Major
> Fix For: Future
>
> Attachments: KYLIN-3071.apache-master.001.patch
>
>
> When calling DictionaryManager.trySaveNewDict, and growing dict is not
> enabled, it only use the history dict which is equal, it may generate many
> dict. We should supply a config to use contains instead of equal to reuse old
> dict.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-3370) Enhance segment pruning
Shaoxiong Zhan created KYLIN-3370: - Summary: Enhance segment pruning Key: KYLIN-3370 URL: https://issues.apache.org/jira/browse/KYLIN-3370 Project: Kylin Issue Type: Improvement Reporter: Shaoxiong Zhan Assignee: Shaoxiong Zhan -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3033) Provide API compatibility for hbase 2.0 release
[ https://issues.apache.org/jira/browse/KYLIN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465469#comment-16465469 ] Shaofeng SHI commented on KYLIN-3033: - Hi Ted, Kylin's branch "master-hadoop3.0-3" is compiled with Hadoop 3.0 and HBase 2.0. While now we're waiting for such a cluster to verify the function. Once Hortonworks or Cloudera released a preview version, we can resume the work there. > Provide API compatibility for hbase 2.0 release > --- > > Key: KYLIN-3033 > URL: https://issues.apache.org/jira/browse/KYLIN-3033 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > Labels: compatibility > > Compiling against hbase 2.0.0-alpha4 release, I got the following compilation > errors: > https://pastebin.com/yfejnTBE > We should start preparing migration to hbase 2.0 compatible APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
