[
https://issues.apache.org/jira/browse/ATLAS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16925946#comment-16925946
]
ASF subversion and git services commented on ATLAS-3405:
--------------------------------------------------------
Commit 4feaae5e35749eed909f4698516a878a95b7facd in atlas's branch
refs/heads/branch-2.0 from Sarath Subramanian
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=4feaae5 ]
ATLAS-3405: Handling of references to non-existing entities in notifications #2
update isEntityIncomplete()
(cherry picked from commit b823084aadd870f8f14df8f01838fac8347e72bb)
> 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.2#803003)
