Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Tue, 30 Aug 2011 07:54:38 +0000 (UTC)
From: "Mohammad Kamrul Islam (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: 
 <484025801.6521.1314690878982.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HADOOP-7592) Provide programmatic access to use
 job log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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