[
https://issues.apache.org/jira/browse/KYLIN-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378253#comment-15378253
]
liyang commented on KYLIN-1869:
-------------------------------
I'm neutral from design point of view. Thus lack of motivation to implement
another version. :-)
We could attach more metadata to snapshot to describe what columns are
contained and support both full and tailored snapshots. If someone want to do
it.
> 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)
