[
https://issues.apache.org/jira/browse/KYLIN-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong Yanghong updated KYLIN-2727:
----------------------------------
Description:
There're several disadvantages to create partial cubes only based on static
rules:
* To learn the concept of these rules will bring extra burden to cube admins
* To achieve a goal cuboid set may need a very complicated set of static rules
* Cube designers may be not familiar with business related query patterns,
resulting in few static rules able to applied
* Static rules created at first may not correct or user query patterns are
changing dynamically
The goal of cube planner is to reduce effort for cube admins to design an
effective partial cube. It owns the following advantages:
* No sophisticated combination of static rules is needed
* Allow more dimensions to be included with few static rules
* Able to adjust a non-cost-effective cuboid set to a cost-effective one based
on historical queries
was:
There're several disadvantages to create partial cubes only based on static
rules:
* To learn the concept of these rules will bring extra burden to cube admins
* To achieve a goal cuboid set may need a very complicated set of static rules
* Cube designers may be not familiar with business related query patterns,
resulting in few static rules able to applied
* Static rules created at first may not correct or user query patterns are
changing dynamically
The goal of cube planner is to reduce effort for cube admins to design an
effective partial cube. It owns the following advantages:
* No sophisticated combination of static rules is needed
* Able to adjust a non-cost-effective cuboid set to a cost-effective one based
on historical
> Introduce cube planner able to select cost-effective cuboids to be built by
> cost-based algorithms
> -------------------------------------------------------------------------------------------------
>
> Key: KYLIN-2727
> URL: https://issues.apache.org/jira/browse/KYLIN-2727
> Project: Kylin
> Issue Type: New Feature
> Affects Versions: v2.0.0
> Reporter: Zhong Yanghong
> Assignee: Zhong Yanghong
>
> There're several disadvantages to create partial cubes only based on static
> rules:
> * To learn the concept of these rules will bring extra burden to cube admins
> * To achieve a goal cuboid set may need a very complicated set of static rules
> * Cube designers may be not familiar with business related query patterns,
> resulting in few static rules able to applied
> * Static rules created at first may not correct or user query patterns are
> changing dynamically
> The goal of cube planner is to reduce effort for cube admins to design an
> effective partial cube. It owns the following advantages:
> * No sophisticated combination of static rules is needed
> * Allow more dimensions to be included with few static rules
> * Able to adjust a non-cost-effective cuboid set to a cost-effective one
> based on historical queries
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
