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

Posted to issues@kylin.apache.org by "jiatao.tao (JIRA)" <ji...@apache.org> on 2017/12/10 04:57:00 UTC

[jira] [Comment Edited] (KYLIN-2964) AclEntity operation issue

    [ https://issues.apache.org/jira/browse/KYLIN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284645#comment-16284645 ] 

jiatao.tao edited comment on KYLIN-2964 at 12/10/17 4:56 AM:
-------------------------------------------------------------

Hi [~julianpan] Could you add some UTs?


was (Author: aron.tao):
Hi [~julianpan] Could add some UTs?

> AclEntity operation issue 
> --------------------------
>
>                 Key: KYLIN-2964
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2964
>             Project: Kylin
>          Issue Type: Bug
>          Components: REST Service
>    Affects Versions: v2.1.0
>            Reporter: Pan, Julian
>            Assignee: Pan, Julian
>         Attachments: KYLIN_2964.patch
>
>
> When user add/update/delete access for AclEntity (project, model, cube, job), which will check user exist. But if there are two user not exist, which will cause issue. Admin want to delete the notExistsUser1, it will throws notExistsUser2 not exist. The other operation has same issues for this check. Could we add another method for checkExistUser and just add the method for add or update? It should be fix this issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)