[
https://issues.apache.org/jira/browse/HIVE-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735391#comment-13735391
]
Hive QA commented on HIVE-4901:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12597134/HIVE-4901.1.patch
{color:green}SUCCESS:{color} +1 2774 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/365/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/365/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.
> Connection should be closed when Statement#execute() failed
> byTTransportException
> ---------------------------------------------------------------------------------
>
> Key: HIVE-4901
> URL: https://issues.apache.org/jira/browse/HIVE-4901
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 0.11.0
> Environment: Ubuntu 11.10
> Reporter: Azrael Park
> Assignee: Azrael Park
> Priority: Trivial
> Attachments: HIVE-4901.1.patch, HIVE-4901.patch
>
>
> Currently, Connection is not closed when Statement#execute() failed by
> TTransportException due to shutdown hiveserver. It means this connection
> can't be used but connection status is still 'not closed'.
> Close connection and throws 'connection is closed' exception from next
> approach.
> {noformat}
> Scenario is as following:
> 1. Client connect hiveserver.
> 2. Hiveserver shutdown.
> 3. Client execute query.
> >>> Client got TTransportException and Connection is closed.
> 4. Hiveserver start.
> 5. Client execute query
> >>> Client got exception messages 'Can't create statement, Connection is
> closed'.
> {noformat}
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
