[
https://issues.apache.org/jira/browse/HIVE-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996038#comment-13996038
]
Hive QA commented on HIVE-7043:
-------------------------------
{color:red}Overall{color}: -1 no tests executed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12644516/HIVE-7043.3.patch
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-Build/186/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-Build/186/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12644516
> When using the tez session pool via hive, once sessions time out, all queries
> go to the default queue
> -----------------------------------------------------------------------------------------------------
>
> Key: HIVE-7043
> URL: https://issues.apache.org/jira/browse/HIVE-7043
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.13.0
> Reporter: Vikram Dixit K
> Assignee: Vikram Dixit K
> Fix For: 0.14.0
>
> Attachments: HIVE-7043.2.patch, HIVE-7043.3.patch
>
>
> When using a tez session pool to run multiple queries, once the sessions time
> out, we always end up using the default queue to launch queries. The load
> balancing doesn't work in this case.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
