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

Posted to dev@atlas.apache.org by "Apoorv Naik (JIRA)" <ji...@apache.org> on 2018/02/14 04:27:00 UTC

[jira] [Updated] (ATLAS-2443) Capture required entity attributes in outgoing DELETE messages

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

Apoorv Naik updated ATLAS-2443:
-------------------------------
    Attachment: 0001-ATLAS-2443-include-unique-attributes-in-entity-delet.patch

> Capture required entity attributes in outgoing DELETE messages
> --------------------------------------------------------------
>
>                 Key: ATLAS-2443
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2443
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.8.1, 0.8.2
>            Reporter: Apoorv Naik
>            Assignee: Apoorv Naik
>            Priority: Major
>         Attachments: 0001-ATLAS-2443-include-unique-attributes-in-entity-delet.patch
>
>
> Right now the outgoing DELETE messages to the ATLAS_ENTITIES topic only capture the typeName and the guid. This is not necessarily enough for the interested parties/applications, instead it is more useful to send out the unique attributes of the entity alongwith some other essential stuff. 
>  
> The extra attributes can be used by relying applications like Ranger to update their policies when HARD DELETE is enabled on Atlas, as once the vertex is deleted the guid etc can not be used with Atlas.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)