[
https://issues.apache.org/jira/browse/KYLIN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339520#comment-15339520
]
陈雷雷 commented on KYLIN-1313:
----------------------------
hi Dong Li
How can I enable this functionalty in the backend myself?
> Enable deriving dimensions on non PK/FK
> ---------------------------------------
>
> Key: KYLIN-1313
> URL: https://issues.apache.org/jira/browse/KYLIN-1313
> Project: Kylin
> Issue Type: Improvement
> Reporter: hongbin ma
> Assignee: hongbin ma
> Fix For: v1.5.2
>
>
> currently derived column has to be columns on look table, and the derived
> host column has to be PK/FK(It's also a problem when the lookup table grows
> every large). Sometimes columns on the fact exhibit deriving relationship
> too. Here's an example fact table:
> (dt date, seller_id bigint, seller_name varchar(100) , item_id bigint,
> item_url varchar(1000), count decimal, price decimal)
> seller_name is uniquely determined by each seller id, and item_url is
> uniquely determined by each item_id. The users does not expect to do
> filtering on columns like seller name or item_url, they just want to retrieve
> it when they do grouping/filtering on other dimensions like selller id, item
> id or even other dimensions like dt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
