[
https://issues.apache.org/jira/browse/KYLIN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068743#comment-17068743
]
ASF subversion and git services commented on KYLIN-3628:
--------------------------------------------------------
Commit e16a4beeaa1c2889c55356a5283f662e908f3122 in kylin's branch
refs/heads/master from yaqian.zhang
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=e16a4be ]
KYLIN-3628 Fix the silently swallow legit exceptions and reduce code duplication
> 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: v2.6.6
>
>
> 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
(v8.3.4#803005)
