You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shao Feng Shi (Jira)" <ji...@apache.org> on 2020/05/27 13:57:00 UTC
[jira] [Closed] (KYLIN-2064) add non-runtime-aggregation measure
support
[ https://issues.apache.org/jira/browse/KYLIN-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shao Feng Shi closed KYLIN-2064.
--------------------------------
Resolution: Won't Fix
> add non-runtime-aggregation measure support
> -------------------------------------------
>
> Key: KYLIN-2064
> URL: https://issues.apache.org/jira/browse/KYLIN-2064
> Project: Kylin
> Issue Type: Improvement
> Affects Versions: v1.5.2
> Reporter: fengYu
> Assignee: fengYu
> Priority: Major
> Attachments: 0001-KYLIN-2064-add-non-runtime-aggregation-measure-for-d.patch
>
>
> Kylin is based on pre-computation and store result in hbase. however, It support runtime aggregation to satisfy the query which can not match computed data.
> But the runtime aggregation slow down the query and need more storage space in hbase(which will slow down scan speed), such as distinct count/ topn measures .
> So we can use more pre-compution and less runtime aggregation, in some scenario we do not need results cross different partition(date), we add a kind of measure which only support result for count distinct, it will speed up query and need less storage.
> what's more, If a query on this measure which is not computed it will return exception.
> I will arrange our solution in my patch later.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)