ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Don Bosco Durai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-698) Ranger policy should support variables like $user
Date Fri, 02 Sep 2016 00:45:20 GMT

    [ https://issues.apache.org/jira/browse/RANGER-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457103#comment-15457103

Don Bosco Durai commented on RANGER-698:

This is really cool. Thanks for implementing this. I have a question how are we allowing {USER}
to be selected in the user drop down? Is it one of the item in the drop down list?

Also, in the future, we should consider creating some default policies. E.g. /home/{USER}
out of the box. 

> Ranger policy should support variables like $user
> -------------------------------------------------
>                 Key: RANGER-698
>                 URL: https://issues.apache.org/jira/browse/RANGER-698
>             Project: Ranger
>          Issue Type: Improvement
>    Affects Versions: 0.7.0
>            Reporter: Don Bosco Durai
>            Assignee: Abhay Kulkarni
>             Fix For: 0.7.0
> It would be good to support variables in resources and users.
> E.g.
> HDFS Resource =  /home/$user  
> or
> Table Resource = ${user}_*
> Users allowed = $user
> Where $user will be expanded to the current user. 
> I think, resource substitution will be easy. For permission, we can use key word like
we use for all users group="public". We can use key word like "USER" or something like that.

This message was sent by Atlassian JIRA

View raw message