[
https://issues.apache.org/jira/browse/HIVE-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839655#comment-13839655
]
Vaibhav Gumashta commented on HIVE-5230:
----------------------------------------
[~thejas] Since JDBC doesn't use async api as of now, I think we can address
error message related changes in
[HIVE-5232|https://issues.apache.org/jira/browse/HIVE-5232] which aims at
making the async execution the default. I'll add a comment there to keep note
of adding relevant tests there.
> 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
> Affects Versions: 0.12.0, 0.13.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Fix For: 0.13.0
>
> Attachments: HIVE-5230.1.patch, HIVE-5230.1.patch, HIVE-5230.2.patch,
> HIVE-5230.3.patch, HIVE-5230.4.patch, HIVE-5230.6.patch, HIVE-5230.7.patch,
> HIVE-5230.8.patch, HIVE-5230.9.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)
