hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-22036) HMS should identify events corresponding to replicated database for Atlas HMS hook
Date Mon, 29 Jul 2019 10:34:00 GMT


Hive QA commented on HIVE-22036:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 16715 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12976105 - PreCommit-HIVE-Build

> HMS should identify events corresponding to replicated database for Atlas HMS hook
> ----------------------------------------------------------------------------------
>                 Key: HIVE-22036
>                 URL:
>             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, HIVE-22036.03.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

View raw message