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 (JIRA)" <ji...@apache.org> on 2018/05/17 01:27:00 UTC
[jira] [Commented] (RANGER-2104) Ranger tagsync should ignore
ENTITY_UPDATE events if the updated entity does not have associated traits
[ https://issues.apache.org/jira/browse/RANGER-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478352#comment-16478352 ]
Abhay Kulkarni commented on RANGER-2104:
----------------------------------------
Patch for master:
https://reviews.apache.org/r/67119/
> Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does not have associated traits
> -------------------------------------------------------------------------------------------------------
>
> Key: RANGER-2104
> URL: https://issues.apache.org/jira/browse/RANGER-2104
> Project: Ranger
> Issue Type: Bug
> Components: tagsync
> Affects Versions: 1.0.0, master, 0.7.1
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Priority: Major
> Fix For: master, 0.7.2, 1.0.1
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)