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 "Thomas Kathmann (JIRA)" <ji...@apache.org> on 2010/04/13 15:22:50 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=12856420#action_12856420 ]
Thomas Kathmann commented on MAPREDUCE-118:
-------------------------------------------
Isn't it just possible to add a getter for RunningJob to JobContext or to use the fix I have suggested earlier? (i.e. set the jobId of Job class after Job is submitted)
Currently I don't know any way in 0.20.x to get the JobID of a job besides manually patching hadoop-core jar
> 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
> Affects Versions: 0.20.1
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: patch-118-0.20.txt, patch-118-0.21.txt, patch-118-1.txt, patch-118.txt
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira