hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharad Agarwal (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-975) Add an API in job client to get the history file url for a given job id
Date Tue, 22 Sep 2009 06:08:16 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758136#action_12758136

Sharad Agarwal commented on MAPREDUCE-975:

bq. it seems obvious that this is missing a test case for a bad jobid. 
The api doesn't check for the validity of the jobid. It just constructs the url based on the
jobid passed. The javadoc of the api says that the history file may or may not be present
depending on the job state.

> Add an API in job client to get the history file url for a given job id
> -----------------------------------------------------------------------
>                 Key: MAPREDUCE-975
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-975
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: client, jobtracker
>            Reporter: Sharad Agarwal
>            Assignee: Sharad Agarwal
>             Fix For: 0.21.0
>         Attachments: 975_v1.patch, 975_v2.patch, 975_v3.patch
> MAPREDUCE-817 added an API to get history url in RunningJob. Similar API should be added
in job client to get the history file given a job id. Something like:
> String getHistoryFile(JobId jobid);

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message