You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Sarath Subramanian (Jira)" <ji...@apache.org> on 2019/09/06 23:23:00 UTC
[jira] [Updated] (ATLAS-3405) Handling of references to
non-existing entities in notifications
[ https://issues.apache.org/jira/browse/ATLAS-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sarath Subramanian updated ATLAS-3405:
--------------------------------------
Description:
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.
was:
Hook notifications containing references to non-existing entities are dropped by Atlas server, with the following error:
{code}
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.
> 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
>
>
> 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)