You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by Abhay Kulkarni <ak...@hortonworks.com> on 2018/05/16 22:04:39 UTC

Re: Review Request 67160: RANGER-2104: Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does not have associated traits

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

(Updated May 16, 2018, 10:04 p.m.)


Review request for ranger and Madhan Neethiraj.


Changes
-------

Updated with Apache JIRA


Summary (updated)
-----------------

RANGER-2104: Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does not have associated traits


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


Repository: ranger


Description (updated)
-------

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
-----

  pom.xml b76e4e30a 
  src/main/assembly/tagsync.xml 26b42cae3 
  tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java 8641d609d 
  tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java 95ff8ec00 


Diff: https://reviews.apache.org/r/67160/diff/1/


Testing (updated)
-------

Tested with a local VM


Thanks,

Abhay Kulkarni