[
https://issues.apache.org/jira/browse/KYLIN-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216173#comment-16216173
]
Shaofeng SHI commented on KYLIN-1892:
-------------------------------------
Hao, the v2 patch looks good except the comment 3. Can it compare with the end
time of the last segment (instead of system current time)? The reasons are 1)
to be consistent with the "retention_range", so that clear to explain to user;
2) would be safer, so when no new segment comes, it won't merge.
Just let me know whether you have any different comment. Thanks!
> Support setting a volatile range for auto merge
> -----------------------------------------------
>
> Key: KYLIN-1892
> URL: https://issues.apache.org/jira/browse/KYLIN-1892
> Project: Kylin
> Issue Type: Improvement
> Components: Job Engine
> Affects Versions: v1.5.2
> Reporter: fengYu
> Assignee: Yang Hao
> Attachments: KYLIN-1892.patch, KYLIN-1892.v2.patch
>
>
> We always has some data need to be amended some days later
> in current kylin, once I set Auto Merge Thresholds, the segment newly build
> will merge if reach Thresholds, the next day refresh will refresh merged
> segemnt, which is unnecessary.
> So I want to add a interval configuration means auto merge will merge
> segments outside of the interval.
> for example, if interval = 2, Auto Merge Thresholds=7, if 07-01 to 07-07 is
> built, auto merge will not trigger, when 07-09 built success, auto merge will
> trigger and merge segments from 07-01 to 07-07.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
