You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhong Yanghong (JIRA)" <ji...@apache.org> on 2016/07/11 22:07:11 UTC

[jira] [Updated] (KYLIN-1870) Allow users to designate job engine at job level

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

Zhong Yanghong updated KYLIN-1870:
----------------------------------
    Summary: Allow users to designate job engine at job level  (was: Allow users to designate job engine)

> Allow users to designate job engine at job level
> ------------------------------------------------
>
>                 Key: KYLIN-1870
>                 URL: https://issues.apache.org/jira/browse/KYLIN-1870
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Job Engine
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>
> For cube building, current rule for selecting a job engine may not be perfect for users. Users may want to choose one job engine to build cube. There is one question related to this. Can we support the designation of job engine at job level? In other words, if we build different segments belonging to a cube by different engines, will it bring some issue, especially when users need to merge those segments?
> If there's no issue, should we provide a restful API for users to do cube building with the designation of job engine?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)