[
https://issues.apache.org/jira/browse/KYLIN-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371233#comment-15371233
]
liyang commented on KYLIN-1869:
-------------------------------
The current design -- take snapshot of all columns -- allows a snapshot be
shared globally, cross cubes and models. Tailor columns will reduce the
snapshot size for one cube, at cost that snapshots become less general, and we
may have to build multiple snapshots for one lookup table.
There are pros and cons on both side.
> 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.3.4#6332)
