hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Bapat (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-22036) HMS should identify events corresponding to replicated database for Atlas HMS hook
Date Fri, 26 Jul 2019 06:15:00 GMT

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

Ashutosh Bapat updated HIVE-22036:
----------------------------------
    Attachment: HIVE-22036.02.patch
        Status: Patch Available  (was: In Progress)

Fix checkstyle comments and test failures from the previous run.

> 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, HIVE-22036.02.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)

Mime
View raw message