hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Drome (JIRA)" <>
Subject [jira] [Commented] (HIVE-4467) HiveConnection does not handle failures correctly
Date Wed, 01 May 2013 22:48:15 GMT


Chris Drome commented on HIVE-4467:

[~cwsteinbach], the issue is with the condition in the verifySuccess method:

if ((status.getStatusCode() != TStatusCode.SUCCESS_STATUS) &&
    (withInfo && (status.getStatusCode() != TStatusCode.SUCCESS_WITH_INFO_STATUS)))

when withInfo is false this condition will always be false. We have seen the case where the
status code is an error and because withInfo is false there is no exception thrown.

Thiruvel's patch addresses this case.
> HiveConnection does not handle failures correctly
> -------------------------------------------------
>                 Key: HIVE-4467
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2, JDBC
>    Affects Versions: 0.11.0, 0.12.0
>            Reporter: Thiruvel Thirumoolan
>            Assignee: Thiruvel Thirumoolan
>             Fix For: 0.11.0, 0.12.0
>         Attachments: HIVE-4467.patch
> HiveConnection uses Utils.verifySuccess* routines to check if there is any error from
the server side. This is not handled well. In Utils.verifySuccess() when withInfo is 'false',
the condition evaluates to 'false' and no SQLexception is thrown even though there could be
a problem on the server.

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:

View raw message