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

Posted to dev@ranger.apache.org by "Velmurugan Periasamy (Jira)" <ji...@apache.org> on 2019/10/24 16:10:00 UTC

[jira] [Updated] (RANGER-2630) Ensure that entity deletes are handled even when Atlas sets deleted entity's state as not ACTIVE

     [ https://issues.apache.org/jira/browse/RANGER-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Velmurugan Periasamy updated RANGER-2630:
-----------------------------------------
    Fix Version/s:     (was: master)
                   2.1.0

> Ensure that entity deletes are handled even when Atlas sets deleted entity's state as not ACTIVE
> ------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-2630
>                 URL: https://issues.apache.org/jira/browse/RANGER-2630
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: master
>            Reporter: Abhay Kulkarni
>            Assignee: Abhay Kulkarni
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> Currently, status of Atlas Entity in the delete notification received by TagSync is ACTIVE. Because of this, current implementation of tagsync works as expected. Tagsync should be able to handle delete operaton even if Atlas decides to set the deleted entity's state to something other than ACTIVE.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)