ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Abhay Kulkarni <akulka...@hortonworks.com>
Subject Re: Review Request 66102: tagsync updates to handle name-services in federated hdfs
Date Sun, 18 Mar 2018 20:49:25 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/66102/
-----------------------------------------------------------

(Updated March 18, 2018, 8:49 p.m.)


Review request for ranger, Apoorv Naik, Madhan Neethiraj, Vishal Suvagia, and Velmurugan Periasamy.


Changes
-------

Addressed review comment


Bugs: RANGER-2024
    https://issues.apache.org/jira/browse/RANGER-2024


Repository: ranger


Description
-------

HDFS entity contained in entity notification includes a name-service-id in case a federated
hdfs file/directory is associated with a classification(i.e. tag). tagsync needs to be able
to handle such entities and map them correctly to appropriate service-resource in Ranger.


Diffs (updated)
-----

  tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasHdfsResourceMapper.java
378542cd8 
  tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasResourceMapper.java 5d067a5b4

  tagsync/src/main/resources/ranger-tagsync-site.xml ea36ed61a 
  tagsync/src/test/java/org/apache/ranger/tagsync/process/TestHdfsResourceMapper.java 627690405



Diff: https://reviews.apache.org/r/66102/diff/2/

Changes: https://reviews.apache.org/r/66102/diff/1-2/


Testing
-------

Developed and passed unit tests.


Thanks,

Abhay Kulkarni


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message