[
https://issues.apache.org/jira/browse/ATLAS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747010#comment-14747010
]
Shwetha G S commented on ATLAS-58:
----------------------------------
Guice doesn't have any support for Service start and stop in servlet handling.
They recommend we create Service interface ourselves -
https://github.com/google/guice/wiki/ModulesShouldBeFastAndSideEffectFree.
Instead of adding shutdown hook in every service, we can as well use
service.stop()
> Make hive hook reliable
> -----------------------
>
> Key: ATLAS-58
> URL: https://issues.apache.org/jira/browse/ATLAS-58
> Project: Atlas
> Issue Type: Sub-task
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Labels: incompatible
> Fix For: trunk
>
> Attachments: ATLAS-58-v2.patch, ATLAS-58.patch
>
>
> Currently, hive hook executes in background thread pool and is an best effort
> approach to register entities. But this needs to be reliable for data
> governance to be effective
> One way is - in hive hook, add the entities to some messaging framework and
> atlas server can read the entities from the message and register in atlas.
> Since, posting message is faster, we can do it synchronously and hence
> reliable entity registration.
> We can start with kafka for messaging, but any other messaging framework
> should be pluggable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
