You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/07/18 08:57:00 UTC
[jira] [Commented] (KYLIN-3917) Add max segment merge span to
cleanup intermediate data of cube building
[ https://issues.apache.org/jira/browse/KYLIN-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887767#comment-16887767 ]
ASF GitHub Bot commented on KYLIN-3917:
---------------------------------------
lshmouse commented on pull request #757: KYLIN-3917: Add max segment merge span to cleanup intermediate data of cube building
URL: https://github.com/apache/kylin/pull/757
See: https://issues.apache.org/jira/browse/KYLIN-3917
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> Add max segment merge span to cleanup intermediate data of cube building
> -------------------------------------------------------------------------
>
> Key: KYLIN-3917
> URL: https://issues.apache.org/jira/browse/KYLIN-3917
> Project: Kylin
> Issue Type: Improvement
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Major
> Fix For: Future
>
>
> Currently the intermediate data of building cube can not be deleted for it maybe used for later cubing merging. But it result in double space used in HDFS.
> In actual scenario, we only need month-level segment span in maximum.
> So if a span of segment is larger than a month, we think it don't need be merged and the intermediate data can be deleted.
> So we can add a config kylin.cube.max-segment-merge.span, default is -1.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)