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

Hive QA commented on HIVE-22873:
--------------------------------



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

{color:red}ERROR:{color} -1 due to build exiting with an error

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12993400/HIVE-22873.03.patch 
was found in seen patch url's cache and a test was probably run already on it. 
Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12993400 - PreCommit-HIVE-Build

> Make it possible to identify which hs2 instance executed a scheduled query
> --------------------------------------------------------------------------
>
>                 Key: HIVE-22873
>                 URL: https://issues.apache.org/jira/browse/HIVE-22873
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-22873.01.patch, HIVE-22873.02.patch, 
> HIVE-22873.03.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> right now only the query_id is shown; in case of multiple hs2 instances the 
> question...users have to resort to grepping the logs for the given query 
> id....



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

Reply via email to