[ https://issues.apache.org/jira/browse/RANGER-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Velmurugan Periasamy resolved RANGER-1357. ------------------------------------------ Resolution: Fixed Patch from https://reviews.apache.org/r/56414/ is committed now. master - https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=e4122919c46bd9fec38a76b27c7e0f5fb98a5f5b ranger-0.7 - https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=37a253d4f175d1fa1b8667d3125a7592e7918529 > tag objects are not removed when attempting a full sync with Atlas tags > ----------------------------------------------------------------------- > > Key: RANGER-1357 > URL: https://issues.apache.org/jira/browse/RANGER-1357 > Project: Ranger > Issue Type: Bug > Components: tagsync > Affects Versions: 0.7.0 > Reporter: Abhay Kulkarni > Assignee: Abhay Kulkarni > Fix For: 0.7.0 > > > Atlas entity which is previously associated with one or more tags, and has > such associations mirrored in ranger-admin database, is modified to have no > tags when tagsync is down or unable to process tag events. A full-sync is now > performed using Atlas REST API to synchronize ranger-admin tag objects with > Atlas objects. It is expected that the tags not in Atlas any more, are > removed from ranger-admin database after full-sync, however, those tags and > their associations with entities are still in the ranger-admin database. -- This message was sent by Atlassian JIRA (v6.3.15#6346)