ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhay Kulkarni (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-2297) getContentSummary validation failure
Date Thu, 29 Nov 2018 20:35:00 GMT

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

Abhay Kulkarni updated RANGER-2297:
-----------------------------------
    Affects Version/s: 1.1.0
        Fix Version/s: 1.1.1
                       master

> getContentSummary validation failure
> ------------------------------------
>
>                 Key: RANGER-2297
>                 URL: https://issues.apache.org/jira/browse/RANGER-2297
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 1.1.0, 1.2.0
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: master, 1.1.1, 1.2.1
>
>
> Parameter values for authorization API call for getContentSummary have changed with fix
for [HDFS-12130|https://issues.apache.org/jira/browse/HDFS-12130]. This causes Ranger authorizer
to fail.
> Ranger authorizer needs to be updated to accommodate for NameNode changes in authorizing
getContentSummary() use-case. Here are the details of the proposed updates:
> Ranger authorizer currently constructs the path to authorize from the given INodeAttributes
>  Ranger authorizer will use the following alternate approach to construct the path -
only when checkPermission() is called with single entry arrays for inodes and inodeAttributes
parameters, and the given inode has a parent.
>  – get path to authorize from the given inode by calling getFullPathName()
>  – if snapshotId != Snapshot.CURRENT_STATE_ID, remove "/.snapshot" from the path obtained
from getFullPathName()



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message