[jira] [Updated] (KYLIN-2363) Prune cuboids by capping number of dimensions

2017-11-28 Thread Roger Shi (JIRA)

 [ 
https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roger Shi updated KYLIN-2363:
-
Description: 
the scene like this:

I have 20+ dimensions, However the query will only use at most 5 dimensions in 
all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) is 
useless.

I think we can add a configuration in cube, which limit the max dimensions that 
cuboid includes.

What's more, we can config which level(number of dimension) need to calculate. 
in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+

=

The dimension capping is turned on by adding dim_cap property in 
aggregation_groups definition.

For example, the following aggregation group sets the dimension cap to 3. All 
cuboids containing more than 3 dimensions  are skipped in this aggregation 
group.

{code:none}

"aggregation_groups" : [ {
"includes" : [ "PART_DT", "META_CATEG_NAME", "CATEG_LVL2_NAME", 
"CATEG_LVL3_NAME", "LEAF_CATEG_ID", "LSTG_FORMAT_NAME", "LSTG_SITE_ID", 
"OPS_USER_ID", "OPS_REGION", 
   "BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL", 
"SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL", "BUYER_ACCOUNT.ACCOUNT_COUNTRY", 
"SELLER_ACCOUNT.ACCOUNT_COUNTRY", "BUYER_COUNTRY.NAME", "SELLER_COUNTRY.NAME" ],
"select_rule" : {
  "hierarchy_dims" : [ [ "META_CATEG_NAME", "CATEG_LVL2_NAME", 
"CATEG_LVL3_NAME", "LEAF_CATEG_ID" ] ],
  "mandatory_dims" : [ "PART_DT" ],
  "joint_dims" : [ [ "BUYER_ACCOUNT.ACCOUNT_COUNTRY", "BUYER_COUNTRY.NAME" 
], [ "SELLER_ACCOUNT.ACCOUNT_COUNTRY", "SELLER_COUNTRY.NAME" ],
   [ "BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL", 
"SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL" ], [ "LSTG_FORMAT_NAME", "LSTG_SITE_ID" 
], [ "OPS_USER_ID", "OPS_REGION" ] ],
 "dim_cap" : 3
}
} ]
{code}

  was:
the scene like this:

I have 20+ dimensions, However the query will only use at most 5 dimensions in 
all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) is 
useless.

I think we can add a configuration in cube, which limit the max dimensions that 
cuboid includes.

What's more, we can config which level(number of dimension) need to calculate. 
in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+


> Prune cuboids by capping number of dimensions
> -
>
> Key: KYLIN-2363
> URL: https://issues.apache.org/jira/browse/KYLIN-2363
> Project: Kylin
>  Issue Type: Improvement
>Reporter: fengYu
>Assignee: Roger Shi
> Fix For: v2.3.0
>
> Attachments: Dimension Capping.md
>
>
> the scene like this:
> I have 20+ dimensions, However the query will only use at most 5 dimensions 
> in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) 
> is useless.
> I think we can add a configuration in cube, which limit the max dimensions 
> that cuboid includes.
> What's more, we can config which level(number of dimension) need to 
> calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+
> =
> The dimension capping is turned on by adding dim_cap property in 
> aggregation_groups definition.
> For example, the following aggregation group sets the dimension cap to 3. All 
> cuboids containing more than 3 dimensions  are skipped in this aggregation 
> group.
> {code:none}
> "aggregation_groups" : [ {
> "includes" : [ "PART_DT", "META_CATEG_NAME", "CATEG_LVL2_NAME", 
> "CATEG_LVL3_NAME", "LEAF_CATEG_ID", "LSTG_FORMAT_NAME", "LSTG_SITE_ID", 
> "OPS_USER_ID", "OPS_REGION", 
>"BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL", 
> "SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL", "BUYER_ACCOUNT.ACCOUNT_COUNTRY", 
> "SELLER_ACCOUNT.ACCOUNT_COUNTRY", "BUYER_COUNTRY.NAME", "SELLER_COUNTRY.NAME" 
> ],
> "select_rule" : {
>   "hierarchy_dims" : [ [ "META_CATEG_NAME", "CATEG_LVL2_NAME", 
> "CATEG_LVL3_NAME", "LEAF_CATEG_ID" ] ],
>   "mandatory_dims" : [ "PART_DT" ],
>   "joint_dims" : [ [ "BUYER_ACCOUNT.ACCOUNT_COUNTRY", 
> "BUYER_COUNTRY.NAME" ], [ "SELLER_ACCOUNT.ACCOUNT_COUNTRY", 
> "SELLER_COUNTRY.NAME" ],
>[ "BUYER_ACCOUNT.ACCOUNT_BUYER_LEVEL", 
> "SELLER_ACCOUNT.ACCOUNT_SELLER_LEVEL" ], [ "LSTG_FORMAT_NAME", "LSTG_SITE_ID" 
> ], [ "OPS_USER_ID", "OPS_REGION" ] ],
>  "dim_cap" : 3
> }
> } ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (KYLIN-2363) Prune cuboids by capping number of dimensions

2017-11-28 Thread Shaofeng SHI (JIRA)

 [ 
https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shaofeng SHI updated KYLIN-2363:

Fix Version/s: v2.3.0

> Prune cuboids by capping number of dimensions
> -
>
> Key: KYLIN-2363
> URL: https://issues.apache.org/jira/browse/KYLIN-2363
> Project: Kylin
>  Issue Type: Improvement
>Reporter: fengYu
>Assignee: Roger Shi
> Fix For: v2.3.0
>
> Attachments: Dimension Capping.md
>
>
> the scene like this:
> I have 20+ dimensions, However the query will only use at most 5 dimensions 
> in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) 
> is useless.
> I think we can add a configuration in cube, which limit the max dimensions 
> that cuboid includes.
> What's more, we can config which level(number of dimension) need to 
> calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (KYLIN-2363) Prune cuboids by capping number of dimensions

2017-04-25 Thread Roger Shi (JIRA)

 [ 
https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roger Shi updated KYLIN-2363:
-
Attachment: Dimension Capping.md

> Prune cuboids by capping number of dimensions
> -
>
> Key: KYLIN-2363
> URL: https://issues.apache.org/jira/browse/KYLIN-2363
> Project: Kylin
>  Issue Type: Improvement
>Reporter: fengYu
> Attachments: Dimension Capping.md
>
>
> the scene like this:
> I have 20+ dimensions, However the query will only use at most 5 dimensions 
> in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) 
> is useless.
> I think we can add a configuration in cube, which limit the max dimensions 
> that cuboid includes.
> What's more, we can config which level(number of dimension) need to 
> calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (KYLIN-2363) Prune cuboids by capping number of dimensions

2017-02-26 Thread liyang (JIRA)

 [ 
https://issues.apache.org/jira/browse/KYLIN-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

liyang updated KYLIN-2363:
--
Summary: Prune cuboids by capping number of dimensions  (was: support limit 
of dimensions in a cuboid)

> Prune cuboids by capping number of dimensions
> -
>
> Key: KYLIN-2363
> URL: https://issues.apache.org/jira/browse/KYLIN-2363
> Project: Kylin
>  Issue Type: Improvement
>Reporter: fengYu
>
> the scene like this:
> I have 20+ dimensions, However the query will only use at most 5 dimensions 
> in all dimensions, so cuboid that contains 5+ dimensions(except base cuboid) 
> is useless.
> I think we can add a configuration in cube, which limit the max dimensions 
> that cuboid includes.
> What's more, we can config which level(number of dimension) need to 
> calculate. in above scene, we only calculate leve 1,2,3,4,5. and skip level 5+



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)