[
https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740760#comment-15740760
]
kangkaisen commented on KYLIN-2239:
-----------------------------------
Hi, Shaofeng.
1. you are right that refresh multiple segments at once is supported, I
remembered wrong.
2. I agree with you that separating "new" and "history" build makes the logic
more clear than combine them together. But actually the "build" type can do
anything and it's function contains the "refresh".
3. I think we can keep "refresh" tag in Web GUI for users to refresh "history"
data and "build" tag to build "new" data, but we both use "build" type actually.
4. I want to remove the "refresh" type , because when I wrote scheduler script
to build production cube in my company, I found the "refresh" type is useless
and I realized all demand only with "build" type.
5 This is not a important issue and it doesn't affect common user. If you think
the "refresh" type is necessary，I could close the issue.
> 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)
