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

Posted to dev@ranger.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2014/09/11 21:59:33 UTC

[jira] [Updated] (ARGUS-40) User denied table access after access is granted via GRANT

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

Madhan Neethiraj updated ARGUS-40:
----------------------------------
    Description: 
Using GRANT statement, SELECT privilege on a table is granted to an user. The user is still denied access to the table.

Note that the policy created by GRANT statement has the column field unpopulated. Once the column field is set to "*", the user is able to access the table. However, subsequent GRANT/REVOKE does not recognize this update policy.


  was:
Using GRANT statement, SELECT privilege on a tables is granted to an user. The user is still denied access to the table.

Note that the policy created by GRANT statement has the column field unpopulated. Once the column field is set to "*", the user is able to access the table. However, subsequent GRANT/REVOKE does not recognize this update policy.



> User denied table access after access is granted via GRANT
> ----------------------------------------------------------
>
>                 Key: ARGUS-40
>                 URL: https://issues.apache.org/jira/browse/ARGUS-40
>             Project: Argus
>          Issue Type: Bug
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>
> Using GRANT statement, SELECT privilege on a table is granted to an user. The user is still denied access to the table.
> Note that the policy created by GRANT statement has the column field unpopulated. Once the column field is set to "*", the user is able to access the table. However, subsequent GRANT/REVOKE does not recognize this update policy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)