You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Na Zhai (JIRA)" <ji...@apache.org> on 2018/12/26 03:22:00 UTC
[jira] [Updated] (KYLIN-3628) The wrong result when a query with
one lookup table
[ https://issues.apache.org/jira/browse/KYLIN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Na Zhai updated KYLIN-3628:
---------------------------
Description: Two cubes use the same lookup table, and then the lookup table data in Hive changes. One of Kylin's cubes builds the new data, and the other doesn't. When Kylin queries the lookup table, there is no mechanism to choose which cube being used. So it maybe get the error result. I have an idea, choose the latest cube to answer the query. (was: Two cubes use the same lookup table, and then the lookup table data in Hive changes. One of Kylin's cubes builds the new data, and the other doesn't. When Kylin queries the lookup table, the data gets confused.)
> The wrong result when a query with one lookup table
> ---------------------------------------------------
>
> 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
>
>
> Two cubes use the same lookup table, and then the lookup table data in Hive changes. One of Kylin's cubes builds the new data, and the other doesn't. When Kylin queries the lookup table, there is no mechanism to choose which cube being used. So it maybe get the error result. I have an idea, choose the latest cube to answer the query.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)