You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Guangyuan Feng (Jira)" <ji...@apache.org> on 2023/06/13 07:34:00 UTC

[jira] [Updated] (KYLIN-5563) Enable operation role has the privilege to manage the model indexes

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

Guangyuan Feng updated KYLIN-5563:
----------------------------------
    Fix Version/s: 5.0-beta
                       (was: 5.0-alpha)

> Enable operation role has the privilege to manage the model indexes
> -------------------------------------------------------------------
>
>                 Key: KYLIN-5563
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5563
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Security
>    Affects Versions: 5.0-alpha
>            Reporter: Guangyuan Feng
>            Assignee: Guangyuan Feng
>            Priority: Major
>             Fix For: 5.0-beta
>
>
> In daily works, we will cooperate with other guys to manage a shared model, generally the model is private, but we can let other roles, especially _*OPERATION role,*_ to have the privilege to manage the indexes on this model.
> But Kylin lacks some manners to easily enable this feature, hence we propose a new property `kylin.index.enable-operator-design` to make it work. When it's true, OPERATIONs can CRUD the indexes, but modify the model.
> Of course, in order to bring in this switch, we have to change the default checks for the related APIs.



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