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

Posted to issues@sentry.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2017/07/10 20:08:00 UTC

[jira] [Updated] (SENTRY-378) Clean up the usage of SentryAccessDeniedException

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

Sergio Peña updated SENTRY-378:
-------------------------------
    Fix Version/s:     (was: 1.8.0)
                   2.0.0

Moving all unresolved jiras with fix version 1.8.0 to 2.0.0. Please change the fix version if you intend to make it into 1.8.0 release.

> Clean up the usage of SentryAccessDeniedException
> -------------------------------------------------
>
>                 Key: SENTRY-378
>                 URL: https://issues.apache.org/jira/browse/SENTRY-378
>             Project: Sentry
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>            Reporter: Sravya Tirukkovalur
>            Assignee: Jan Hentschel
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: SENTRY-378.001.patch, SENTRY-378.002.patch, SENTRY-378.002.patch
>
>
> SentryAccessDeniedException is mostly used when user does is not part of sentry admin group, but is trying to create role, grant role or grant privilege.  Although I see that it is also used else where, there is scope for some clean up. For example:
> SentryStore.getMSentryVersion()



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