[
https://issues.apache.org/jira/browse/KYLIN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888673#comment-16888673
]
ASF subversion and git services commented on KYLIN-3628:
--------------------------------------------------------
Commit d659542ed28e6dcb12a9e6944214258f4eefc178 in kylin's branch
refs/heads/master-hadoop3.1 from XiaoxiangYu
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=d659542 ]
KYLIN-3628 Fix unexpected exception for select from Lookup Table
In some case, cube returned by findLatestSnapshot didn't contains the snapshot
table
for what you need. Because some dimension which exists in model but was removed
in cube design phase, query such as "select * from LookupTable" will throw
unexpected exception and confused user.
> Query with lookup table always use latest snapshot
> --------------------------------------------------
>
> Key: KYLIN-3628
> URL: https://issues.apache.org/jira/browse/KYLIN-3628
> Project: Kylin
> Issue Type: Improvement
> Reporter: Na Zhai
> Assignee: Na Zhai
> Priority: Major
> Fix For: v3.0.0-alpha2
>
>
> If user queries a lookup table, Kylin will randomly selects a Cube (which has
> the snapshot of this lookup table) to answer it. This causes uncertainty when
> there are multiple cubes (share the same lookup): some cubes are newly built,
> some not. If Kylin picks an old cube, the query result is old.
> To remove this uncertainty, for such queries, either always use latest
> snapshot, or use earlist snapshot. We believe the "latest" version is better.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
