[
https://issues.apache.org/jira/browse/SENTRY-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653977#comment-14653977
]
Hadoop QA commented on SENTRY-827:
----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12748684/SENTRY-827.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/754/console
This message is automatically generated.
> Server Scope always grants ALL
> -------------------------------
>
> Key: SENTRY-827
> URL: https://issues.apache.org/jira/browse/SENTRY-827
> Project: Sentry
> Issue Type: Bug
> Reporter: Ryan P
> Assignee: Ryan P
> Attachments: SENTRY-827.patch, SENTRY-827.patch.1
>
>
> In it's current state the following two commands result in ALL on SERVER
> server1:
> GRANT SELECT ON SERVER server1 TO ROLE read_role;
> GRANT INSERT ON SERVER server1 TO ROLE insert_role;
> This can cause users to unknowingly grant full privileges to user groups.
> Fixing this behavior will also allow us to mimic the previous behavior
> exhibited with Policy Files:
> read_role = server=server1->db=*->table=*->action=select
> insert_role = server=server1->db=*->table=*->action=insert
> Granting SELECT on SERVER would be far more pleasant than granting SELECT on
> each individual DATABASE
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
