You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Vaibhav Gumashta (JIRA)" <ji...@apache.org> on 2013/10/12 01:08:42 UTC

[jira] [Commented] (HIVE-5230) Better error reporting by async threads in HiveServer2

    [ https://issues.apache.org/jira/browse/HIVE-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793120#comment-13793120 ] 

Vaibhav Gumashta commented on HIVE-5230:
----------------------------------------

[~prasadm] Thanks for the patch Prasad. I have a few comments on the current approach though: I'll post them soon. My thoughts are mostly on having a unified approach to report errors on both sync and async operations. 

> 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: Prasad Mujumdar
>             Fix For: 0.13.0
>
>         Attachments: HIVE-5230.1.patch, HIVE-5230.1.patch
>
>
> [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 was sent by Atlassian JIRA
(v6.1#6144)