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 Thu, 11 Aug 2016 01:24:22 GMT

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

Don Bosco Durai commented on RANGER-698:

We have to select the right format for the variable. Some templates use {{var}}, while others
use %var%. We also need to consider escape character. We can make the choice based on the
library we are going to use to parse the string. If it is going to be regex, then we can come
with something on our own.

If we are going to use fixed values, which is going to be the case here, then, {user} or {USER}
should also work. So we just have to search for the exact string. 

> Ranger policy should support variables like $user
> -------------------------------------------------
>                 Key: RANGER-698
>                 URL: https://issues.apache.org/jira/browse/RANGER-698
>             Project: Ranger
>          Issue Type: Improvement
>            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