[
https://issues.apache.org/jira/browse/KYLIN-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194784#comment-15194784
]
liyang commented on KYLIN-1482:
-------------------------------
Historic query patterns is a good source of cuboid optimization. Cuboids that a
never queried for example, could be pruned in future build.
> [UMBRELLA] optimize the cuboids to be computed
> ----------------------------------------------
>
> Key: KYLIN-1482
> URL: https://issues.apache.org/jira/browse/KYLIN-1482
> Project: Kylin
> Issue Type: Task
> Affects Versions: v1.5.0
> Reporter: hongbin ma
> Assignee: hongbin ma
>
> As known to many the number of cuboids is exponential to the number of
> dimensions. Currently in the latest dev branch, Kylin adopt a well designed
> pruning scheme called "New Aggregation Group"
> (http://kylin.apache.org/blog/2016/02/18/new-aggregation-group/) that allows
> user to specify relationships between dimensions for cuboid pruning. The
> rule-based approach is simple and effective in many situations.
> However the rule-based approach also has its limitations: It will fail to
> capture potential prunings when the cube designer does not fully understand
> how the cube will be used, or the nature of the relationship between
> parent/child cuboid. In this case, we need to provide more flexible tools for
> cube designer to optimize which cuboids to be computed and which not to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
