[
https://issues.apache.org/jira/browse/HIVE-22036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895135#comment-16895135
]
Hive QA commented on HIVE-22036:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12976105/HIVE-22036.03.patch
{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:
https://builds.apache.org/job/PreCommit-HIVE-Build/18191/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/18191/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-18191/
Messages:
{noformat}
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
{noformat}
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: 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,
> 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
(v7.6.14#76016)
