You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2017/11/29 06:57:00 UTC

[jira] [Commented] (KYLIN-1869) When building snapshot for lookup tables, should we build those dimensions used by model or the whole

    [ https://issues.apache.org/jira/browse/KYLIN-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270272#comment-16270272 ] 

Shaofeng SHI commented on KYLIN-1869:
-------------------------------------

[~yaho]yanghong, what's the status of it? please update status in time.

> When building snapshot for lookup tables, should we build those dimensions used by model or the whole
> -----------------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-1869
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1869
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Job Engine
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>
> Currently when building a snapshot for a lookup table, the input is the whole value set of the lookup table, which may be not so reasonable. In some cases, a lookup table owns tens columns. However, the columns used by a model or a cube is only a few, 1 to 5. Those unused columns will make the snapshot too large, which will bring burdens for both storing and loading.



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