[
https://issues.apache.org/jira/browse/HIVE-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801310#action_12801310
]
Zheng Shao commented on HIVE-1032:
----------------------------------
I went over the code again. Actually the flag "isMapTask" is used in
"MapAggrMemErrorHeuristic".
However "MapAggr" can actually happen in reducer. The reason is that we always
put the operators to the reducer of the former map-reduce job, instead of the
mapper of the latter map-reduce job. We should remove that check.
> Better Error Messages for Execution Errors
> ------------------------------------------
>
> Key: HIVE-1032
> URL: https://issues.apache.org/jira/browse/HIVE-1032
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Query Processor
> Reporter: Paul Yang
> Assignee: Paul Yang
> Attachments: HIVE-1032.1.patch, HIVE-1032.2.patch, HIVE-1032.3.patch
>
>
> Three common errors that occur during execution are:
> 1. Map-side group-by causing an out of memory exception due to large
> aggregation hash tables
> 2. ScriptOperator failing due to the user's script throwing an exception or
> otherwise returning a non-zero error code
> 3. Incorrectly specifying the join order of small and large tables, causing
> the large table to be loaded into memory and producing an out of memory
> exception.
> These errors are typically discovered by manually examining the error log
> files of the failed task. This task proposes to create a feature that would
> automatically read the error logs and output a probable cause and solution to
> the command line.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
