[
https://issues.apache.org/jira/browse/KYLIN-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720890#comment-16720890
]
ASF subversion and git services commented on KYLIN-3718:
--------------------------------------------------------
Commit f031005e4bd61dc6340c221d9fcbc16fa2024777 in kylin's branch
refs/heads/master from [~temple.zhou]
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=f031005 ]
KYLIN-3718 Segments in volatile range is more than designated value
> Segments in volatile range is more than designated value
> --------------------------------------------------------
>
> Key: KYLIN-3718
> URL: https://issues.apache.org/jira/browse/KYLIN-3718
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
> Affects Versions: v2.3.0, v2.4.0, v2.5.0
> Reporter: Temple Zhou
> Assignee: Temple Zhou
> Priority: Major
> Fix For: v2.6.0
>
> Attachments: KYLIN-3718.master.001.patch
>
>
> I have designated the volatile value of the cube to 1 and the auto merge
> thresholds is 3, but I found the former 3 segments was not merged when the
> 4th segment was ready.
> the ready segments are as below:
> # xxx[20181201000000_20181202000000]
> # xxx[20181202000000_20181203000000]
> # xxx[20181203000000_20181204000000]
> # xxx[20181204000000_20181205000000]
> Besides, I found the log info:
> {code:java}
> segment in volatile range: xxx[20181203000000_20181204000000]
> segment in volatile range: xxx[20181204000000_20181205000000]{code}
> I think the expected result should be:
> seg: xxx[20181204000000_20181205000000] should be reserved
> seg:
> xxx[20181201000000_20181202000000],xxx[20181202000000_20181203000000],xxx[20181203000000_20181204000000]
> should be merged.
> However, the truth is:
> When the 5th segments was ready, the former 3 segments were automatically
> merged.
> Although the value of volatile range is 1, there are always 2 segments will
> be reserved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
