[
https://issues.apache.org/jira/browse/SENTRY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084400#comment-16084400
]
Hadoop QA commented on SENTRY-378:
----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12876886/SENTRY-378.003.patch
against master.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/3018/console
This message is automatically generated.
> 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, SENTRY-378.003.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)
