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

Hive QA commented on HIVE-20936:
--------------------------------



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

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

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

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

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

> Allow the Worker thread in the metastore to run outside of it
> -------------------------------------------------------------
>
>                 Key: HIVE-20936
>                 URL: https://issues.apache.org/jira/browse/HIVE-20936
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>            Reporter: Jaume M
>            Assignee: Jaume M
>            Priority: Major
>         Attachments: HIVE-20936.1.patch, HIVE-20936.2.patch, 
> HIVE-20936.3.patch, HIVE-20936.4.patch, HIVE-20936.5.patch, 
> HIVE-20936.6.patch, HIVE-20936.7.patch
>
>
> Currently the Worker thread in the metastore in bounded to the metastore, 
> mainly because of the TxnHandler that it has. This thread runs some map 
> reduce jobs which may not only be an option wherever the metastore is 
> running. A solution for this can be to run this thread in HS2 depending on a 
> flag.



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

Reply via email to