[
https://issues.apache.org/jira/browse/MAPREDUCE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856735#action_12856735
]
Amareshwari Sriramadasu commented on MAPREDUCE-118:
---------------------------------------------------
The solution proposed for trunk is "Get the jobid for a job in constructor
itself", but this contradicts with MAPREDUCE-1505, which creates the RPC client
lazily. We have to rethink about the solution here. We might have to set the
jobid after the job submission as Thomas suggested.
Thoughts?
> 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
