[
https://issues.apache.org/jira/browse/KYLIN-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712228#comment-16712228
]
ASF GitHub Bot commented on KYLIN-3628:
---------------------------------------
shaofengshi commented on a change in pull request #359: KYLIN-3628 The wrong
result when a query with one lookup table
URL: https://github.com/apache/kylin/pull/359#discussion_r239672931
##########
File path: core-cube/src/main/java/org/apache/kylin/cube/CubeInstance.java
##########
@@ -717,4 +724,51 @@ public static CubeSegment findSegmentWithJobId(String
jobID, CubeInstance cubeIn
throw new IllegalStateException("No segment's last build job ID equals
" + jobID);
}
+ public CubeInstance findLastSnapshot(List<RealizationEntry>
realizationEntries, String lookupTableName) {
Review comment:
CubeInstance is not the best place to put such a method. Please move it to
CubeManager.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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, the data gets confused.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
