You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhong Yanghong (JIRA)" <ji...@apache.org> on 2016/09/08 08:54:20 UTC

[jira] [Commented] (KYLIN-1900) Cube new build override old one

    [ https://issues.apache.org/jira/browse/KYLIN-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473274#comment-15473274 ] 

Zhong Yanghong commented on KYLIN-1900:
---------------------------------------

How about this?

Repro steps:
1. build a cube from time 20120101 – 20140101, trigger the build from REST API
2. build the same cube from 20120101 – 20130101, trigger the build from REST API

It seems the second segment will not be excluded by the method "calculateToBeSegments" of "CubeManager". However, the first segment will be deleted after invoking the method "promoteNewlyBuiltSegments" of "CubeManager". Is this behavior by design?

> Cube new build override old one
> -------------------------------
>
>                 Key: KYLIN-1900
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1900
>             Project: Kylin
>          Issue Type: Test
>          Components: Job Engine
>    Affects Versions: v1.5.3
>            Reporter: Roger Shi
>
> Repro steps:
> 1. build a cube from time 20120101 -- 20130101, trigger the build from REST API
> 2. build the same cube from 20120101 -- 20140101, trigger the build from REST API
> The second build will override the first one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)