You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Billy Liu (JIRA)" <ji...@apache.org> on 2018/01/25 10:50:00 UTC
[jira] [Commented] (KYLIN-1892) Support setting a volatile range
for auto merge
[ https://issues.apache.org/jira/browse/KYLIN-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339067#comment-16339067 ]
Billy Liu commented on KYLIN-1892:
----------------------------------
Hello [~yanghaogn], thank you for this contributing. May I know the unit of the volatile range? day? millisecond? I found from the front-end : "or 'Auto Merge' will not merge latest [Volatile Range] days cube segments." So the unit is day?
> 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
> Priority: Major
> Fix For: v2.3.0
>
> Attachments: KYLIN-1892.v3.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
(v7.6.3#76005)