[
https://issues.apache.org/jira/browse/MAPREDUCE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791873#action_12791873
]
Amareshwari Sriramadasu commented on MAPREDUCE-118:
---------------------------------------------------
The proposal looks fine.
But I found small issue implementing it. In 0.21, ClientProtocol.getNewJobID()
throws InterruptedException out. The new Job constructors(introduced in 0.21)
can be changed to throw InterruptedException. But, the deprecated constructors
cannot be changed.
After discussing with Arun, one solution we could think of is "add a deprecated
setJobID in JobContextImpl, which can be called from deprecated constructors.
Will remove the newly added method, when we remove the deprecated constructors".
> 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.20.2
>
> Attachments: patch-118-0.20.txt, patch-118-0.21.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.
-
You can reply to this email to add a comment to the issue online.
