You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "Vsevolod Ostapenko (Jira)" <ji...@apache.org> on 2019/09/26 16:55:00 UTC

[jira] [Reopened] (KYLIN-3628) Query with lookup table always use latest snapshot

     [ https://issues.apache.org/jira/browse/KYLIN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vsevolod Ostapenko reopened KYLIN-3628:
---------------------------------------

The most recent change will silently swallow legit exceptions in the findLatestSnapshot and may result in an incorrect cube instance to be returned, effectively re-introducing the original bug for cases when there is an exception.

> 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, v2.6.4
>
>
> 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)