hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-118) Job.getJobID() will always return null
Date Fri, 01 Apr 2011 01:28:06 GMT

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

Chris Douglas commented on MAPREDUCE-118:
-----------------------------------------

I committed the ported fix to branch-0.20-security. Thanks, Dick!

> 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
>          Components: client
>    Affects Versions: 0.20.1
>            Reporter: Amar Kamat
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.20.3, 0.20.204.0
>
>         Attachments: MAPREDUCE-118--0-20-3.patch, patch-118-0.20-1.txt, patch-118-0.20.txt,
patch-118-0.21.txt, patch-118-1.txt, patch-118-2.txt, patch-118-3.txt, patch-118-4.txt, patch-118-5.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message