[ATLAS-512] Decouple currently integrating components from availability of Atlas service for raising metadata events

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.7-incubating
• Assignee: Hemanth Yamijala
• Reporter: Hemanth Yamijala
• Created: 23/Feb/16 11:57
• Updated: 08/Apr/16 07:09
• Resolved: 10/Mar/16 20:25

Description

The components that currently integrate with Atlas (Hive, Sqoop, Falcon, Storm) all communicate their metadata events using Kafka as a messaging layer. This effectively decouples these components from the Atlas server.

However, all of these components have some initialization that checks if their respective models are registered with Atlas. For components that integrate on the server, like HiveServer2 and Falcon, this initialization is a one time check and hence, is manageable. Others like Sqoop, Storm and the Hive CLI are client side components and hence the initialization happens for every run or session of these components. Invoking the initialization (and the one time check) every time like this effectively means that the Atlas server should be always available.

This JIRA is to try and remove this dependency and thus truly decouple these components.

Issue Links

• blocks: AMBARI-14920 Support Atlas / Storm integration
• contains: ATLAS-338 Notifications to Kafka from a new Hive client don't come if Atlas server is down
• relates to: ATLAS-454 Storm hook is missing jersey client dependencies
• links to: Review board request for ATLAS-512