[
https://issues.apache.org/jira/browse/HIVE-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777006#comment-13777006
]
Prasad Mujumdar commented on HIVE-5230:
---------------------------------------
[~vaibhavgumashta] Hi Vaibhav, I have a patch that to address the basic error
handling. It's mainly to capture the exception from async query and return it
on subsequent client requests like fetch. I think it can be integrated with the
HIVE-5217, the async polling work that you are doing to raise error on status
check.
I will go ahead and assign the ticket to myself and post the patch. Let me know
if you think its conflicting with your other async query work. Thanks!
> Better error reporting by async threads in HiveServer2
> ------------------------------------------------------
>
> Key: HIVE-5230
> URL: https://issues.apache.org/jira/browse/HIVE-5230
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Fix For: 0.13.0
>
>
> [HIVE-4617|https://issues.apache.org/jira/browse/HIVE-4617] provides support
> for async execution in HS2. When a background thread gets an error, currently
> the client can only poll for the operation state and also the error with its
> stacktrace is logged. However, it will be useful to provide a richer error
> response like thrift API does with TStatus (which is constructed while
> building a Thrift response object).
--
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
