You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "guohuili (JIRA)" <ji...@apache.org> on 2016/05/25 14:40:12 UTC

[jira] [Commented] (KYLIN-242) Redesign aggregation group

    [ https://issues.apache.org/jira/browse/KYLIN-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300153#comment-15300153 ] 

guohuili commented on KYLIN-242:
--------------------------------

I don't know what's the grammar used in kylin.

> Redesign aggregation group
> --------------------------
>
>                 Key: KYLIN-242
>                 URL: https://issues.apache.org/jira/browse/KYLIN-242
>             Project: Kylin
>          Issue Type: Improvement
>          Components: General
>            Reporter: Luke Han
>            Assignee: hongbin ma
>              Labels: github-import
>             Fix For: v1.5.0
>
>
> Proposal from Hongbin about Cuboid White List:
> * More detail, please refer to Kylin Dev mailing list: dev@kylin.incubator.apache.org 
> Logically, a cube contains cuboids representing all combinations of
> dimensions. Apparently, a naive cube building strategy that materializes
> all cuboids will easily meet curse-of-dimension problems. Currently Kylin
> leverages a strategy called "aggregation groups" to reduce the number of
> cuboids need being materialized.
> However, if the query pattern is simple and fixed, the "aggregation group"
> strategy is still not efficient enough. For example, suppose there're five
> dimensions, namely A,B,C,D and E. The data modeler is sure that only
> combinations (A,B,C), (D,E), (A,E) will be queried, so he’ll use the
> aggregation group tool to optimize his cube definition. However, whatever
> aggregation group he chooses, lots of useless combinations would be
> materialized.
> With a new strategy called "cuboid whitelist", data modelers can guide
> Kylin to only materialize the cuboids he's interested in. Depending on the
> whitelist, Kylin will materialize the minimal set of cuboids to cover each
> cuboid in the whitelist. To support this, the following functionalities
> should be added:
> 1. Front-end/UI for specifying whitelist members, and persistent them to
> cube description.
> 2. Enhanced job engine scheduler that will calculate a minimal spanning
> build tree based on the whitelist.
> 3. (OPTIONAL) Enhanced job engine to support dynamic whitelist, trigger new
> builds for lately added whitelist members.
> Hongbin Ma
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/KylinOLAP/Kylin/issues/263
> Created by: [lukehan|https://github.com/lukehan]
> Labels: enhancement, 
> Milestone: Backlog
> Assignee: [binmahone|https://github.com/binmahone]
> Created at: Thu Dec 25 13:17:11 CST 2014
> State: open



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)