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 67178: RANGER-2104: Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does not have associated traits
Date Thu, 17 May 2018 03:13:27 GMT

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

(Updated May 17, 2018, 3:13 a.m.)


Review request for ranger and Madhan Neethiraj.


Changes
-------

Addressed review comment.


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


Repository: ranger


Description
-------

Tagsync may receive a large number of ENTITY_UPDATE events when used in a large EDW environment.
If an update entity is not associated with any tags (aka traits, classifications), then this
event does not have material impact on the resource->tag associations in the Ranger, and
therefore, can be safely dropped. Processing such event adds processing overhead to tagsync,
ranger-admin and network, and also causes ranger-admin database to be populated with service-resource
that is not tagged and is not needed for access evaluation.


Diffs (updated)
-----

  pom.xml c7632bac9 
  src/main/assembly/tagsync.xml 0b17151b9 
  tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java
f007ae55e 
  tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java c382db018



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

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


Testing
-------

Tested with local VM


Thanks,

Abhay Kulkarni


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