Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <786472677.1261003338287.JavaMail.jira@brutus>
Date: Wed, 16 Dec 2009 22:42:18 +0000 (UTC)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-118) Job.getJobID() will always return
 null
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Owen O'Malley commented on MAPREDUCE-118:
-----------------------------------------

+1

I think you either need to give it the jobid or it gets one from the job tracker in the constructor.

> 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.