You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Andrew Sherman (JIRA)" <ji...@apache.org> on 2017/12/15 17:46:00 UTC
[jira] [Commented] (HIVE-18283) Better error message and error code
for HoS exceptions
[ https://issues.apache.org/jira/browse/HIVE-18283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292899#comment-16292899 ]
Andrew Sherman commented on HIVE-18283:
---------------------------------------
As the new getHiveException() method could be fragile, is it worth having a unit test that exercises it with some actual errror messages?
> Better error message and error code for HoS exceptions
> ------------------------------------------------------
>
> Key: HIVE-18283
> URL: https://issues.apache.org/jira/browse/HIVE-18283
> Project: Hive
> Issue Type: Improvement
> Components: Spark
> Reporter: Chao Sun
> Assignee: Chao Sun
> Attachments: HIVE-18283.0.patch
>
>
> Right now HoS only use a few error codes. For the majority of the errors, user will see an error code 1 followed by a lengthy stacktrace. This is not ideal since:
> 1. It is often hard to find the root cause - sometimes it is hidden deeply inside the stacktrace.
> 2. After identifying the root cause, it is not easy to find a fix. Often user have to copy & paste the error message and google them.
> 3. It is not clear whether the error is transient or not, depending on which user may want to retry the query.
> To improve the above, this JIRA propose to assign error code & canonical error messages for different HoS errors. We can take advantage of the existing {{ErrorMsg}} class.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)