[
https://issues.apache.org/jira/browse/HIVE-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870785#comment-13870785
]
Hive QA commented on HIVE-6184:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12622760/HIVE-6184.1.patch.txt
{color:green}SUCCESS:{color} +1 4924 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/900/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/900/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: 12622760
> Bug in SessionManager.stop() in HiveServer2
> -------------------------------------------
>
> Key: HIVE-6184
> URL: https://issues.apache.org/jira/browse/HIVE-6184
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: Jaideep Dhok
> Attachments: HIVE-6184.1.patch.txt
>
>
> The conf setting hive.server2.async.exec.shutdown.timeout is set to a long
> value (10L) in HiveConf.java, but it is read using getIntVar in
> SessionManager.stop.
> Instead it should be read as -
> {code}
> long timeout =
> hiveConf.getLongVar(ConfVars.HIVE_SERVER2_ASYNC_EXEC_SHUTDOWN_TIMEOUT);
> {code}
> Current code will either cause an assertion error if assertions are enabled,
> or it would return the timeout as -1 if the property is not set in
> hive-site.xml
> Workaround is to explicitly set the property in hive-site.xml
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
