[
https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739837#comment-15739837
]
Shaofeng SHI commented on KYLIN-2239:
-------------------------------------
Kaisen, actually refresh multiple segments at once is supported I rember:
specify the startOffset as the first segment's start, and endOffset as the last
segment's end; The only limitation is the web GUI hasn't been updated, but it
should be easy to change.
For streaming case, the Web GUI has been updated for both build and refresh;
Separating "new" and "history" build makes the logic more clear than combine
them together; ,what's the problem you see with as-is design?
> 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)
