[
https://issues.apache.org/jira/browse/RANGER-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-698:
------------------------------------
Fix Version/s: 0.6.3
Committed to ranger-0.6 branch:
- http://git-wip-us.apache.org/repos/asf/incubator-ranger/commit/dc873cb2
- http://git-wip-us.apache.org/repos/asf/incubator-ranger/commit/c599bbb4
- http://git-wip-us.apache.org/repos/asf/incubator-ranger/commit/dd8a5817
Thanks for the backport [~abhayk].
> 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, 0.6.3
>
> Attachments: RANGER-698.1.patch
>
>
> 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
(v6.3.4#6332)
