[
https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740795#comment-15740795
]
Shaofeng SHI commented on KYLIN-2239:
-------------------------------------
Hi Kaisen,
>From API point of view, I want to keep it as stable as possible; even to
>change, still need consider the backward compitable; So I suggest keep it;
>Maybe someday Kylin will extend here, the current design keeps flexibility.
So far for the scheduler script, you can use the "build" type for both history
and new data;
> 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)
