[
https://issues.apache.org/jira/browse/KYLIN-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479097#comment-17479097
]
ASF GitHub Bot commented on KYLIN-5155:
---------------------------------------
sleep1661 commented on pull request #1800:
URL: https://github.com/apache/kylin/pull/1800#issuecomment-1017126242
@hit-lacus @zhangayqian @zhengshengjun could you help take a look when you
have time? Thanks.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Change volatile range default value
> -----------------------------------
>
> Key: KYLIN-5155
> URL: https://issues.apache.org/jira/browse/KYLIN-5155
> Project: Kylin
> Issue Type: Improvement
> Components: Job Engine
> Affects Versions: v4.0.1
> Reporter: hujiahua
> Priority: Major
>
> Since the current default value of `Volatile Range` is 0, when segment merge
> job is triggered, this new segment which generated today may also be merged.
> This brings up two issue: 1. Rebuid cube job triggered by scheduling system
> (e.g. apache airflow) with kylin rest API will failed because of using today
> startTime and endTime. 2. The segment of today was hot data (visited
> frequently), so query RT may get worse after merged. So I proposal not to
> merge last 7 days data by default.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
