atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ATLAS-512) Decouple currently integrating components from availability of Atlas service for raising metadata events
Date Tue, 23 Feb 2016 11:58:18 GMT
Hemanth Yamijala created ATLAS-512:
--------------------------------------

             Summary: Decouple currently integrating components  from availability of Atlas
service for raising metadata events
                 Key: ATLAS-512
                 URL: https://issues.apache.org/jira/browse/ATLAS-512
             Project: Atlas
          Issue Type: Sub-task
            Reporter: Hemanth Yamijala


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message