hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-118) Job.getJobID() will always return null
Date Mon, 10 May 2010 04:28:49 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amareshwari Sriramadasu updated MAPREDUCE-118:
----------------------------------------------

    Status: Open  (was: Patch Available)

Test failures seem unrelated. The failures are because of NoClassDefFoundError.
Rerunning through hudson

> 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.21.0
>
>         Attachments: 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.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.


Mime
View raw message