[
https://issues.apache.org/jira/browse/KYLIN-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367331#comment-15367331
]
Zhong Yanghong commented on KYLIN-1855:
---------------------------------------
I'm just a little worried about the function of model. If we allow the cubes
created based on the same model to be based on different star schema, then it's
better to change the "create flat table" step. Adding additional join may
influence the SQL parse step which should remove those joins. Otherwise, when
query, kylin may have to load useless lookup table snapshot.
> Should exclude those joins in whose related lookup tables no dimensions are
> used in cube
> ----------------------------------------------------------------------------------------
>
> Key: KYLIN-1855
> URL: https://issues.apache.org/jira/browse/KYLIN-1855
> Project: Kylin
> Issue Type: Improvement
> Reporter: Zhong Yanghong
> Assignee: Zhong Yanghong
>
> A cube is based on a model in which a star schema is defined. In some cases,
> the cube utilizes only a few lookup tables rather than all. In this case,
> when creating the sql for the flat table, those lookup tables should not be
> included. Otherwise, it will confuse users when query. If users do query
> according to the definition of the flat table, error of no realization will
> occur due to lack of the related join.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
