[
https://issues.apache.org/jira/browse/SENTRY-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603597#comment-16603597
]
Hadoop QA commented on SENTRY-2315:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12938292/SENTRY-2315.2.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/4085/console
This message is automatically generated.
> The grant all operation is not dropping the create/alter/drop/index/lock
> privileges.
> ------------------------------------------------------------------------------------
>
> Key: SENTRY-2315
> URL: https://issues.apache.org/jira/browse/SENTRY-2315
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.1.0
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Priority: Major
> Attachments: SENTRY-2315.1.patch, SENTRY-2315.2.patch
>
>
> When an object has the ALL privilege, any individual privilege explicitly
> granted (i.e. create, select, insert, ...) after that has no effect on the
> privilege list because ALL implies the role or user has all those privileges.
> However, when any of the new privileges list (create, alter, drop) is granted
> before, and then the grant ALL happens, those privileges are not removed. We
> should keep the GRANT ALL consistent and remove any individual privilege
> (except the OWNER privilege) from the list.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
