[ 
https://issues.apache.org/jira/browse/HIVE-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill Graham updated HIVE-795:
-----------------------------

    Attachment: HIVE-795.1.patch

Attaching HIVE-795.1.patch, which included the changes discussed above. A few 
things to note:

- Error messages and SQLStates are now included in {{HiveServerException}}. 
Please review changes to this class carefully. The existing comment in that 
class regarding how this file is auto-generated by thrift and not to edit it 
unless you know what you're doing has me a bit concerned. :)

- Error messages from the {{Driver}} classes compile step are captured and 
returned to the client, along with corresponding SQLStates. The exception 
handling of the {{ql.parse}} package made it possible to return informative 
error messages.

- Errors from the {{Driver}} classes execute step are another story. This code 
relies on {{Task.executeTask()}}, which swallows exceptions and returns just 
status codes. Refactoring this to return a composite could be a considerable 
task, so this should be done as part of a separate JIRA IMO. The server still 
returns error messages and SQLStates for execution errors though. It's just 
that the error messages the server has as it's disposal could be improved.

- The {{HiveConnection}} constructor now throws {{SQLException}} instead of 
{{Exception}}.

> Return better error messaging from HiveServer 
> ----------------------------------------------
>
>                 Key: HIVE-795
>                 URL: https://issues.apache.org/jira/browse/HIVE-795
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Server Infrastructure
>            Reporter: Bill Graham
>            Assignee: Bill Graham
>         Attachments: HIVE-795.1.patch
>
>
> If an exception is thrown on the Hive server (i.e., when an invalid query is 
> passed), the Hive server throws a HiveServerExcpeption to the client with a 
> message like "Query returned non-zero code: 10". A more informative 
> description of the cause of the error should be returned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to