You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "YongChul Kwon (JIRA)" <ji...@apache.org> on 2009/09/25 00:50:16 UTC

[jira] Commented: (MAPREDUCE-118) Job.getJobID() will always return null

    [ https://issues.apache.org/jira/browse/MAPREDUCE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759300#action_12759300 ] 

YongChul Kwon commented on MAPREDUCE-118:
-----------------------------------------

With the new API, JobID is only available through JobClient instance which is protected by Job class. The mapreduce.Job.getJobID() should override JobContext.getJobID() to read it form JobClient once it is submitted.

> Job.getJobID() will always return null
> --------------------------------------
>
>                 Key: MAPREDUCE-118
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-118
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Amar Kamat
>
> JobContext is used for a read-only view of job's info. Hence all the readonly fields in JobContext are set in the constructor. Job extends JobContext. When a Job is created, jobid is not known and hence there is no way to set JobID once Job is created. JobID is obtained only when the JobClient queries the jobTracker for a job-id., which happens later i.e upon job submission.

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