[jira] [Commented] (ATLAS-3405) Handling of references to non-existing entities in notifications

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ATLAS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042398#comment-17042398 ] 

ASF subversion and git services commented on ATLAS-3405:
--------------------------------------------------------

Commit 9cc59d449d63237bc33a2263eb8ed1e5eae52dd9 in atlas's branch refs/heads/branch-0.8 from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=9cc59d4 ]

ATLAS-3405: Handling of references to non-existing entities in notifications


> Handling of references to non-existing entities in notifications
> ----------------------------------------------------------------
>
>                 Key: ATLAS-3405
>                 URL: https://issues.apache.org/jira/browse/ATLAS-3405
>             Project: Atlas
>          Issue Type: New Feature
>          Components:  atlas-core
>    Affects Versions: 2.0.0
>            Reporter: Sarath Subramanian
>            Assignee: Sarath Subramanian
>            Priority: Major
>             Fix For: 2.1.0
>
>         Attachments: ATLAS-3405.001.patch
>
>
> Hook notifications containing references to non-existing entities are dropped by Atlas server, with the following error:
> {code:java}
>  AtlasObjectId\{guid='null', typeName='hive_db', uniqueAttributes={qualifiedName:db1@prod}} is not found
> {code}
> Instead of dropping such notifications, it will help to create an entity for the reference, and complete processing of the notifications. Such entities will only have its unique-attribute populated, however will capture the lineage and other relationships. When Atlas receives details of the entity in a subsequent notification, Atlas will have rest of the attributes populated as well.



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