You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2017/09/27 05:19:00 UTC
[jira] [Commented] (KYLIN-2872) Incorrect argument order in
CubeManager#calculateHoles()
[ https://issues.apache.org/jira/browse/KYLIN-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181987#comment-16181987 ]
Shaofeng SHI commented on KYLIN-2872:
-------------------------------------
This is expected; It is seeking the holes between the segments. If the first and second segments are not consecutive, will report a hole whose start is the first's end, and the end is the second's start position.
> Incorrect argument order in CubeManager#calculateHoles()
> --------------------------------------------------------
>
> Key: KYLIN-2872
> URL: https://issues.apache.org/jira/browse/KYLIN-2872
> Project: Kylin
> Issue Type: Bug
> Reporter: Ted Yu
> Priority: Minor
>
> {code}
> if (first.isOffsetCube()) {
> hole.setSegRange(new SegmentRange(first.getSegRange().end, second.getSegRange().start));
> {code}
> The arguments to SegmentRange are reversed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)