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

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: atlas-core
• Assignee: Sarath Subramanian
• Reporter: Sarath Subramanian
• Created: 06/Sep/19 23:22
• Updated: 22/Feb/20 06:40
• Resolved: 09/Sep/19 01:08

Description

Hook notifications containing references to non-existing entities are dropped by Atlas server, with the following error:

 AtlasObjectId\{guid='null', typeName='hive_db', uniqueAttributes={qualifiedName:db1@prod}} is not found

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.

Issue Links

• links to: Code review