You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Arjun Mishra (JIRA)" <ji...@apache.org> on 2019/01/26 21:07:00 UTC

[jira] [Updated] (SENTRY-2490) When building a full perm update for each object we only build 1 privilege per role

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

Arjun Mishra updated SENTRY-2490:
---------------------------------
    Summary: When building a full perm update for each object we only build 1 privilege per role  (was: NN is unfamiliar with REFRESH or CREATE privileges and sets FSAction to NONE on the group when it sees it in a full update)

> When building a full perm update for each object we only build 1 privilege per role
> -----------------------------------------------------------------------------------
>
>                 Key: SENTRY-2490
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2490
>             Project: Sentry
>          Issue Type: Bug
>          Components: Sentry
>    Affects Versions: 2.1.0
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>            Priority: Major
>
> When NN tries to get the FS action on Sentry managed paths, it checks against the ACTION_MAPPING map values. Currently this dataset doesn't have REFRESH or CREATE listed. When NN sees a REFRESH or CREATE privilege it will flag it as unsupported and set the FS action as NONE on that path for that group. This seems to happen only with full update. It will also override any other privilege that group had on that path



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)