ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Velmurugan Periasamy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-2087) Use qualifiedName first to figure out HDFS path, clusterName and Ranger service-name from Atlas Hdfs entity
Date Mon, 02 Jul 2018 19:59:00 GMT

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

Velmurugan Periasamy updated RANGER-2087:
-----------------------------------------
    Fix Version/s:     (was: master)
                   1.1.0

> Use qualifiedName first to figure out HDFS path, clusterName and Ranger service-name
from Atlas Hdfs entity
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-2087
>                 URL: https://issues.apache.org/jira/browse/RANGER-2087
>             Project: Ranger
>          Issue Type: Bug
>          Components: tagsync
>    Affects Versions: master
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Major
>             Fix For: 1.1.0
>
>
> Tagsync uses a mapper class to map Atlas Entity to Ranger Service Resource for each of
the components supported by Atlas. All mappers except Hdfs mapper first parse distinguished-name
of Atlas Entity to build Ranger Service Resource. Hdfs mapper needs to work the same way.



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

Mime
View raw message