Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 26 Sep 2013 16:44:03 +0000 (UTC)
From: "Prasad Mujumdar (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12667177.1378413287786.25008.1380213843524@arcas>
In-Reply-To: <JIRA.12667177.1378413287786@arcas>
References: <JIRA.12667177.1378413287786@arcas>
Subject: [jira] [Commented] (HIVE-5230) Better error reporting by async
 threads in HiveServer2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Prasad Mujumdar commented on HIVE-5230:
---------------------------------------

[~brocknoland] Thanks for taking a look.
Each new exec request will create a new operations object. For a given query , the operation (and hence the backgrond exception) won't be shared with other background exec threads.
                
> 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 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