[
https://issues.apache.org/jira/browse/KYLIN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877286#comment-16877286
]
Vsevolod Ostapenko commented on KYLIN-3628:
-------------------------------------------
[~hit_lacus], I build local 2.6.2 with your changes applied on top and
"derived" column check removed.
It seems to work as intended.
One suggestion though, debug message about overriding cube selection in the
findLatestSnapshot() should be logged only when cube selection was really
overridden. For example:
{code:java}
if (!cube.equals(cubeInstance)) {
logger.debug("Picked cube {} over {} as it provides a more recent snapshot of
the lookup table {}", cube, cubeInstance, lookupTableName);
}
{code}
> 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.0
>
>
> 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.3#76005)
