You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2011/08/31 07:13:09 UTC
[jira] [Commented] (HADOOP-7592) Provide programmatic access to use
job log
[ https://issues.apache.org/jira/browse/HADOOP-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094309#comment-13094309 ]
Suresh Srinivas commented on HADOOP-7592:
-----------------------------------------
Mohammad, this should be created as MapReduce bug right?
> Provide programmatic access to use job log
> -------------------------------------------
>
> Key: HADOOP-7592
> URL: https://issues.apache.org/jira/browse/HADOOP-7592
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Mohammad Kamrul Islam
>
> Since hadoop job/task log is critical for debugging, providing a programmatic access would definitely add a big value to the end user.
> Oozie users are repeatedly asking to open up the hadoop job log for them. However, Oozie doesn't have any knowledge about the log location as well as the log contents of hadoop job.
> The expected programmatic access could come in any or both ways:
> 1. Allowing an API such as getLogPath(jobId) that returns the base HDFS path of the job directory.
> 2. Allowing an API such as getLog(jobId) that will return the log contents (may be as streaming output).
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira