hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Lento (JIRA)" <>
Subject [jira] Commented: (HIVE-1731) Improve miscellaneous error messages
Date Thu, 09 Dec 2010 23:13:03 GMT


Thomas Lento commented on HIVE-1731:

FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask 

The actual error was something to do with my regexp_extract syntax: 

index out of bounds error, no group 1 

I didn't specify a group in the regexp, and when I made the adjustment everything worked as
expected. It seems like this should be caught earlier, or at least the error trace for the
task with the most failures (or a random task with max_failures if there's more than one)
should be dumped to the CLI. 

This one might belong in a different task, since it's a much harder problem to deal with the
error traces for arbitrary functions (or, worse, custom scripts). However, in general "return
code 2" is not useful. It only tells me I need to do a bunch of work to find out what's broken,
and the only reason I know that is because I've been using Hive for a long time.

I think in general "Return code 2" should indicate a problem with the query execution and
include a pointer to the jobtracker logs, or (ideally) a pointer to the log output for the
task(s) with the most failures (maybe the top 10 if there are a lot of tasks with max_failures).

> Improve miscellaneous error messages
> ------------------------------------
>                 Key: HIVE-1731
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: John Sichi
>             Fix For: 0.7.0
> This is a place for accumulating error message improvements so that we can update a bunch
in batch.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message