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

Hive QA commented on HIVE-21646:
--------------------------------



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

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

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL 
https://issues.apache.org/jira/secure/attachment/12969179/HIVE-21646.1.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: 12969179 - PreCommit-HIVE-Build

> Tez: Prevent TezTasks from escaping thread logging context
> ----------------------------------------------------------
>
>                 Key: HIVE-21646
>                 URL: https://issues.apache.org/jira/browse/HIVE-21646
>             Project: Hive
>          Issue Type: Bug
>          Components: Tez
>            Reporter: Gopal V
>            Assignee: Gopal V
>            Priority: Major
>         Attachments: HIVE-21646.1.patch, HIVE-21646.1.patch
>
>
> If hive.exec.parallel is set to true to parallelize MoveTasks or StatsTasks, 
> the Tez task does not benefit from a new thread and will lose all the thread 
> context of the current query.
> Multiple threads even if they are spawned, will lock on SyncDagClient & make 
> progress sequentially.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to