[ 
https://issues.apache.org/jira/browse/HIVE-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038382#comment-13038382
 ] 

jirapos...@reviews.apache.org commented on HIVE-2156:
-----------------------------------------------------



bq.  On 2011-05-23 20:03:10, John Sichi wrote:
bq.  > ql/src/java/org/apache/hadoop/hive/ql/exec/JobDebugger.java, line 84
bq.  > <https://reviews.apache.org/r/777/diff/1/?file=19535#file19535line84>
bq.  >
bq.  >     Any fallback we should try if IOException occurs?

Besides propagating an error message to notify the user that something has gone 
wrong in grabbing the debugging information, not much can be done here. I can 
definitely add a console.print statement with an additional error though


- Syed


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/777/#review707
-----------------------------------------------------------


On 2011-05-24 04:29:32, Syed Albiz wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/777/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2011-05-24 04:29:32)
bq.  
bq.  
bq.  Review request for hive and John Sichi.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  - Add local error messages to point to job logs and provide TaskIDs
bq.  - Add a timeout to the fetching of task logs and errors
bq.  
bq.  
bq.  This addresses bug HIVE-2156.
bq.      https://issues.apache.org/jira/browse/HIVE-2156
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    build-common.xml 00c3680 
bq.    common/src/java/org/apache/hadoop/hive/conf/HiveConf.java dc96a1f 
bq.    conf/hive-default.xml 159d825 
bq.    ql/build.xml 449b47a 
bq.    ql/src/java/org/apache/hadoop/hive/ql/exec/HadoopJobExecHelper.java 
4717c25 
bq.    ql/src/java/org/apache/hadoop/hive/ql/exec/JobDebugger.java PRE-CREATION 
bq.    ql/src/java/org/apache/hadoop/hive/ql/exec/MapRedTask.java 53769a0 
bq.    ql/src/java/org/apache/hadoop/hive/ql/exec/MapredLocalTask.java 691f038 
bq.    ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java 
9cb407c 
bq.    ql/src/test/queries/clientnegative/minimr_broken_pipe.q PRE-CREATION 
bq.    ql/src/test/results/clientnegative/dyn_part3.q.out 5f4df65 
bq.    ql/src/test/results/clientnegative/minimr_broken_pipe.q.out PRE-CREATION 
bq.    ql/src/test/results/clientnegative/script_broken_pipe1.q.out d33d2cc 
bq.    ql/src/test/results/clientnegative/script_broken_pipe2.q.out afbaa44 
bq.    ql/src/test/results/clientnegative/script_broken_pipe3.q.out fe8f757 
bq.    ql/src/test/results/clientnegative/script_error.q.out c72d780 
bq.    ql/src/test/results/clientnegative/udf_reflect_neg.q.out f2082a3 
bq.    ql/src/test/results/clientnegative/udf_test_error.q.out 5fd9a00 
bq.    ql/src/test/results/clientnegative/udf_test_error_reduce.q.out ddc5e5b 
bq.    ql/src/test/templates/TestNegativeCliDriver.vm ec13f79 
bq.  
bq.  Diff: https://reviews.apache.org/r/777/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  Tested TestNegativeCliDriver in both local and miniMR mode
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Syed
bq.  
bq.



> Improve error messages emitted during task execution
> ----------------------------------------------------
>
>                 Key: HIVE-2156
>                 URL: https://issues.apache.org/jira/browse/HIVE-2156
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Syed S. Albiz
>            Assignee: Syed S. Albiz
>         Attachments: HIVE-2156.1.patch, HIVE-2156.2.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: http://www.atlassian.com/software/jira

Reply via email to