[
https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739793#comment-15739793
]
kangkaisen commented on KYLIN-2239:
-----------------------------------
Hi, Shaofeng.
1 The "refresh" buildType only could build existing one segment not whole
history data or multiple segments. I think which doesn't match the "refresh"
semantic completely. Besides, the "build" type could replace the "refresh"
type completely.
2 for the streaming case, whether we only need do some change in web ui? I
think which isn't buildType issue.
If I think wrong, please correct me. thanks.
> Remove refresh buildType
> ------------------------
>
> Key: KYLIN-2239
> URL: https://issues.apache.org/jira/browse/KYLIN-2239
> Project: Kylin
> Issue Type: Improvement
> Reporter: kangkaisen
> Assignee: kangkaisen
> Priority: Minor
>
> currently, we have three build types：build, refresh, merge. But the build
> and the refresh type only is one job type indeed and the build type could
> replace the refresh type completely.
> So, I think the refresh type is redundant. we can firstly remove
> refreshSegment in JobService internal and keep the web api unchanged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
