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

liyang commented on KYLIN-1960:
-------------------------------

I think the latest master has fixed the problem in a slightly different way.

https://issues.apache.org/jira/browse/KYLIN-1744

Basically user can BUILD [t2,t4) without having to merge S2, S3 first. Maybe 
you can have a try on master branch?

> Provide a new build type called COVER
> -------------------------------------
>
>                 Key: KYLIN-1960
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1960
>             Project: Kylin
>          Issue Type: New Feature
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>         Attachments: provide_a_new_build_type_COVER.patch
>
>
> The current three build types are not good at dealing with incremental 
> building with refreshing old data. 
> For example, there are [S1, S2, S3] segments in a cube. S1 with time range 
> [t1, t2); S2 with time range [t2, t3); S3 with time range [t3, t4). 
> Now users want to refresh the old data within [t2, t4). The current strategy 
> is to merge S2 and S3 firstly. Then refresh the bigger segment with time 
> range [t2, t4). The first step is meaningless and wasteful. 
> What if users want to build a new segment with time range [t2, t5), where t5 
> is larger than t4. The current strategy is clumsy.
> How about providing a new build type? Here, it's called COVER. For this type, 
> users also should provide start time and end time as parameters. The start 
> time should match the boundaries of segments. In this case, it should be in 
> set {t1, t2, t3, t4}. While the end time should be larger than t4, or match 
> one of the end times of existing segments. In this case, it should be in set 
> {t2, t3, t4}. Of course, the end time should be larger than the start time. 
> What job engine will do with this build type is as follows:
> 1. first build a new segment with the time range;
> 2. then the covered segments will be deleted.



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

Reply via email to