You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "liyang (JIRA)" <ji...@apache.org> on 2015/09/30 14:22:05 UTC
[jira] [Updated] (KYLIN-444) Support derived on hierarchy columns
[ https://issues.apache.org/jira/browse/KYLIN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liyang updated KYLIN-444:
-------------------------
Issue Type: Wish (was: Improvement)
> Support derived on hierarchy columns
> ------------------------------------
>
> Key: KYLIN-444
> URL: https://issues.apache.org/jira/browse/KYLIN-444
> Project: Kylin
> Issue Type: Wish
> Components: Metadata
> Reporter: Luke Han
> Assignee: liyang
> Labels: github-import
> Fix For: Backlog
>
>
> Currently, **derived** only works for dimension level. When query on high level derived column, it will scan joined key (detail level) which is not cost-efficiency way.
> To avoid too much scan on such derived column, enable derived on hierarchy columns:
> One Sample:
> ```
> {
> "id": "2",
> "name": "category",
> "table": "test_category_groupings",
> "join": {
> "type": "left",
> "primary_key": ["leaf_categ_id", "site_id"],
> "foreign_key": ["leaf_categ_id", "lstg_site_id"]
> },
> "hierarchy": [
> {
> "level": "1",
> "column": "meta_categ_name",
> "derived":["meta_categ_id","meta_desc"]
> },
> {
> "level": "2",
> "column": "categ_lvl2_name",
> "derived":["categ_lvl2_id"]
> },
> {
> "level": "3",
> "column": "categ_lvl3_name",
> "derived":["categ_lvl3_id"]
> }
> ]
> },
> ```
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/KylinOLAP/Kylin/issues/61
> Created by: [lukehan|https://github.com/lukehan]
> Labels: enhancement,
> Created at: Mon Nov 17 16:40:03 CST 2014
> State: open
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)