[
https://issues.apache.org/jira/browse/HIVE-22036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892690#comment-16892690
]
Ashutosh Bapat commented on HIVE-22036:
---------------------------------------
Atlas HMS hook implements only 6 events. This patch adds a flag to these events
indicate whether an event was produced by replication flow. We could, in
general, make this flag available in all the events but there are 37 of those.
For every event we will need to assess whether we can infer the replication
scope for that event, add the code and also add tests for it. Given that Atlas
uses only 6 events, the work for rest of the 31 would not be used immediately
or forever.
> HMS should identify events corresponding to replicated database for Atlas HMS
> hook
> ----------------------------------------------------------------------------------
>
> Key: HIVE-22036
> URL: https://issues.apache.org/jira/browse/HIVE-22036
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Reporter: Ashutosh Bapat
> Assignee: Ashutosh Bapat
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-22036.01.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> An HMS Atlas hook allows an Atlas to create/update/delete its metadata based
> on the corresponding events in HMS. But Atlas replication happens out-side
> and before the Hive replication. Thus any events generated during replication
> may change the Atlas data already replicated, thus interfering with Atlas
> replication. Hence, provide an HMS interface which the hook can use to
> identify the events caused by Hive replication flow.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
