kylin version: 2.2.0
hadoop version: 2.6.0
CDH: 5.8.0





------------------ ???????? ------------------
??????:&nbsp;"Yaqian Zhang"<[email protected]&gt;;
????????:&nbsp;2019??12??9??(??????) ????3:41
??????:&nbsp;"user"<[email protected]&gt;;

????:&nbsp;Re: kylin??????cube????????????



Hi wenhui:

It??s a strange problem.


Can you provide your Kylin version and Hadoop enviornment? I will try to 
reproduce this.

?? 2019??12??9????14:59???????? <[email protected]&gt; ??????

I know your meaning ,the number of READY segments met the conditions of auto 
merge, but&nbsp; auto merge was not triggered, the picture as follows:
<[email protected]&gt;
my poverty as follows:
<[email protected]&gt;


------------------ ???????? ------------------
??????:&nbsp;"ztp"<[email protected]&gt;;
????????:&nbsp;2019??12??9??(??????) ????2:32
??????:&nbsp;"user"<[email protected]&gt;;

????:&nbsp;Re: kylin??????cube????????????





Hi Wenhui,

Only if your number of segments  exceed the Auto Merge Thresholds, the 
independent segments will be merged.


For example: there are 3 segments originally and you build the cube today, so, 
there will be 4 segments totally. But 4 < 7, the 4 segments will not be merged.


If you really do not want there are more segments, you can adjust the Auto 
Merge Thresholds to 1 or 2 days.



BTW: The Retention Threshold may be misleading, it is used to guarantee the 
recent xx days segments will be not merged as the recent segments may be 
refreshed separately.

On Mon, Dec 9, 2019 at 2:05 PM ?????? <[email protected]&gt; wrote:

??????
&nbsp; &nbsp; &nbsp; 
????????cube??????????????????????????????????????????????????
&nbsp; &nbsp; &nbsp; Cube ???????????? &gt; ???????????????? &gt; ????????????
      ????????????????????kylin.cube.is-automerge-enabled &nbsp;?? true&nbsp; 
&nbsp;
&nbsp; &nbsp; &nbsp; ????????cube??Refresh Setting??????????Auto Merge 
Thresholds ?? 7 Days, 28 Days??Retention Threshold?? 0
??????????????????????cube????????????????????????Hbase????????????????segments&nbsp;

Reply via email to