[
https://issues.apache.org/jira/browse/MAPREDUCE-6844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856056#comment-15856056
]
Jason Lowe commented on MAPREDUCE-6844:
---------------------------------------
bq. Since Job history server only shows successful MR jobs
The MapReduce job history server shows all completed jobs, successful, failed,
or killed. If the history server only showed successful jobs, how would users
normally view and debug their failed jobs?
> JobHistoryServer: Create table as statement failed but Job is shown on job
> history server
> -----------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6844
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6844
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 1.2.1
> Reporter: amit gupta
>
> Executed one hive script "Create table <tableName1> as select * from
> <tableName2>".
> hive script execution resulted in an error as tableName1 is of 1000
> characters long.
> *Expectations:* Since Job history server only shows successful MR jobs, It
> should not show this job.
> *Actual:* I am able to see the executed MR job on job history server.
> Hive log:
> FAILED: Execution Error, return code 1 from
> org.apache.hadoop.hive.ql.exec.MoveTask
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
