[ 
https://issues.apache.org/jira/browse/HIVE-21851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053835#comment-17053835
 ] 

Hive QA commented on HIVE-21851:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12995788/HIVE-21851.06.patch

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

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

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/20986/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20986/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20986/

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: 12995788 - PreCommit-HIVE-Build

> FireEventResponse should include event id when available
> --------------------------------------------------------
>
>                 Key: HIVE-21851
>                 URL: https://issues.apache.org/jira/browse/HIVE-21851
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>         Attachments: HIVE-21851.01.patch, HIVE-21851.02.patch, 
> HIVE-21851.03.patch, HIVE-21851.04.patch, HIVE-21851.05.patch, 
> HIVE-21851.06.patch
>
>
> The metastore API {{fire_listener_event}} gives clients the ability to fire a 
> INSERT event on DML operations. However, the returned response is empty 
> struct. It would be useful to sent back the event id information in the 
> response so that clients can take actions based of the event id.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to