You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "kangkaisen (JIRA)" <ji...@apache.org> on 2016/11/30 14:10:59 UTC

[jira] [Updated] (KYLIN-2239) Remove refreshSegment in JobService

     [ https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kangkaisen updated KYLIN-2239:
------------------------------
    Description: 
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.

  was:
currently, we have three build types：build, refresh, merge.  But the build and t 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.


> Remove refreshSegment in JobService
> -----------------------------------
>
>                 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)