[
https://issues.apache.org/jira/browse/KYLIN-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358783#comment-15358783
]
hongbin ma commented on KYLIN-1313:
-----------------------------------
Unfortunately, there's no webUI for extended column yet. we're still working
on it.
You can edit the cube desc json directly, refer to
KYLIN_HOME/examples/test_case_data/localmeta/cube_desc/test_kylin_cube_without_slr_desc.json
as an example, we have two extended column measure there: SITE_EXTENDED_1 and
SITE_EXTENDED_2. besides the measure part, you need SITE_EXTENDED_1 and
SITE_EXTENDED_2 added in "hbase_mapping" as well
after you manually edit the cube desc json, you also need to erase the line
"signature", so that a new cube desc signature can be automatically generated.
> 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)
