hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ning Zhang (JIRA)" <>
Subject [jira] [Commented] (HIVE-2156) Improve error messages emitted during task execution
Date Wed, 03 Aug 2011 07:33:27 GMT


Ning Zhang commented on HIVE-2156:

Syed, there are still 2 tests failed on: mapjoin_hook.q and auto_join25.q. All other tests

> Improve error messages emitted during task execution
> ----------------------------------------------------
>                 Key: HIVE-2156
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Syed S. Albiz
>            Assignee: Syed S. Albiz
>         Attachments: HIVE-2156.1.patch, HIVE-2156.2.patch, HIVE-2156.4.patch, HIVE-2156.8.patch
> Follow-up to HIVE-1731
> A number of issues were related to reporting errors from task execution and surfacing
these in a more useful form.
> Currently a cryptic message with "Execution Error" and a return code and class name of
the task is emitted.
> The most useful log messages here are emitted to the local logs, which can be found through
jobtracker. Having either a pointer to these logs as part of the error message or the actual
content would improve the usefulness substantially. It may also warrant looking into how the
underlying error reporting through Hadoop is done and if more information can be propagated
up from there.
> Specific issues raised in  HIVE-1731:
> FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask
> * issue was in regexp_extract syntax
> FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask
> * tried: desc table_does_not_exist;

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message