[jira] [Resolved] (ATLAS-338) Notifications to Kafka from a new Hive client don't come if Atlas server is down

["Hemanth Yamijala (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ATLAS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hemanth Yamijala resolved ATLAS-338.
------------------------------------
    Resolution: Fixed

As part of ATLAS-512, we have decoupled the hooks from depending on Atlas server for registering the models. I just tested this with master:

* Setup has external Kafka
* With Atlas down, I launched hive and created two tables
* Verified messages have reached Kafka topic ATLAS_HOOK.
* Brought up Atlas, it picked up the messages and populated them properly.
* Queries Atlas UI for the hive tables and got back results as expected.

So closing this bug based on this testing.


> Notifications to Kafka from a new Hive client don't come if Atlas server is down 
> ---------------------------------------------------------------------------------
>
>                 Key: ATLAS-338
>                 URL: https://issues.apache.org/jira/browse/ATLAS-338
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Hemanth Yamijala
>
> Kafka 0.8.2 set up separately.
> Atlas configured to talk to this instance of Kafka.
> Hive hook configured to send events to this topic.
> Steps to reproduce:
> * Register Hive hook to talk to Kafka
> * Bring up Atlas server
> * Write a simple bash script that repeatedly executes Hive DDLs (for e.g. hive -e "create table ..."
> *  While the script is running, bring down the Atlas server with a kill -9
> * The script continues to execute and complete.
> Verify the number of events in the Kafka topic ATLAS_HOOK. When starting fresh, they should be at least equal to the number of tables created by the script. 
> However, the observation is that there are no notifications after the Atlas server was brought down.



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