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

Madhan Neethiraj resolved RANGER-5367.
--------------------------------------
    Fix Version/s: 3.0.0
                   2.8.0
       Resolution: Fixed

* master branch: 
https://github.com/apache/ranger/commit/073bd9fb43f8a3f3f55353cf90c5ad691db24651
 * ranger-2.8 branch: 
https://github.com/apache/ranger/commit/ed998c827db2feed98462c529f127b822daad59f

> simplify resourceName parsing
> -----------------------------
>
>                 Key: RANGER-5367
>                 URL: https://issues.apache.org/jira/browse/RANGER-5367
>             Project: Ranger
>          Issue Type: Sub-task
>          Components: pdp
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Major
>             Fix For: 3.0.0, 2.8.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Authz APIs introduced in RANGER-5309 support name of the accessed resource to 
> be provided as a string, instead of a map used in plugin APIs. For example:
>  * a column:
>  ** Authz APIs: {{column:db1.tbl1.col1}}
>  ** plugin APIs: {{{ "database": "db1", "table": "tbl1", "column": "col1" }}}
>  * an ozone key:
>  ** Authz APIs: {{key:vol1.bucket1/p1/p2/file.txt}}
>  ** plugin APIs: {{{ "volume": "vol1", "bucket": "bucket1", "key": 
> "p1/p2/file.txt" }}}
> The string format is easier to read than the map format, and will result in 
> smaller payloads as well. However, the parsing introduced in RANGER-5309 
> supported more complex constructs like: prefix, suffix, different separators 
> between resources. These are unnecessary, given the need is to capture 
> hierarchy of resources. Hence, I propose to simplify the resource name format 
> to:
>  * remove support for prefix and suffix in resource names
>  ** {{key:ofs://vol1/bucket1/p1/p2/file.txt}} will not be supported; this 
> resource should be specified as {{key:vol1/bucket1/p1/p2/file.txt}}
>  * use only "/" as the separator, with option to escape using backslash (\)
>  ** {{relativepath:container1@account1/p1/p2/file.txt}} will not be 
> supported; this resource should be specified as 
> {{relativepath:account1/container/p1/p2/file.txt}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to