You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "wuxinqiang (Jira)" <ji...@apache.org> on 2022/12/09 08:38:00 UTC

[jira] [Updated] (KYLIN-5358) Whether kylin4 can support building cubes by priority

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

wuxinqiang updated KYLIN-5358:
------------------------------
    Description: 
In business scenarios, there are three types of job: daily incrementally built job, automatically triggered merge job, and batch build tasks for creating or refreshing all data. Tasks should have priority to ensure that high-priority tasks are built first. But kylin currently does not support building cubes by priority.

Although the interface for submitting job tasks in kylin4 has a priorityOffset field, it is not used. Is it possible to use this priorityOffset field and configure PriorityFetcherRunner to implement priority construction of high-priority tasks.

  was:
In business scenarios, there are three types of job: daily incrementally built job, automatically triggered merge job, and batch build job generated by the business for swiping numbers and creating new cubes. Tasks should have priority to ensure that high-priority tasks are built first. But kylin currently does not support building cubes by priority.

Although the interface for submitting job tasks in kylin4 has a priorityOffset field, it is not used. Is it possible to use this priorityOffset field and configure PriorityFetcherRunner to implement priority construction of high-priority tasks.


> Whether kylin4 can support building cubes by priority
> -----------------------------------------------------
>
>                 Key: KYLIN-5358
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5358
>             Project: Kylin
>          Issue Type: Wish
>            Reporter: wuxinqiang
>            Priority: Major
>
> In business scenarios, there are three types of job: daily incrementally built job, automatically triggered merge job, and batch build tasks for creating or refreshing all data. Tasks should have priority to ensure that high-priority tasks are built first. But kylin currently does not support building cubes by priority.
> Although the interface for submitting job tasks in kylin4 has a priorityOffset field, it is not used. Is it possible to use this priorityOffset field and configure PriorityFetcherRunner to implement priority construction of high-priority tasks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)