Thanks Harsh. - Nitin On 6 September 2011 10:56, Harsh J <[email protected]> wrote:
> It is a bug in 0.20.203. You're hitting > https://issues.apache.org/jira/browse/MAPREDUCE-118 > > It was finally backported in 0.20.204 now, so you may use that instead > as it has just released. Also, FWIW, the CDH3 stable distro has > carried that fix for over a year now. > > I'd advise not using the new API though, it is marked unstable and has > some problems and missing components/features. Stick to the stable API > for 0.20.20x, IMHO. > > On Mon, Sep 5, 2011 at 6:31 PM, Nitin Khandelwal > <[email protected]> wrote: > > Hi All, > > > > We are migrating from Hadoop 0.19.2 to Hadoop 0.20.203. The normal flow ( > > job posting / running ) works fine. In one of the flow, we are required > to > > check Task Reports for a running Job to fetch its state. > > > > In the older code (0.19.2) we had following piece of code which does the > > required tasks > > > > runningJob is an instance of Job > > > > TaskReport[] reports = jobClient.getMapTaskReports( > > runningJob.getID()); > > > > Wanted to know how it will change in the newer version. I tried with > > > > TaskReport[] reports = jobClient.getMapTaskReports((JobID) > > runningJob.getJobID()); > > > > This did not work as there is no JobID is set in Job instance. > > > > Requesting your assistance in this. > > > > Let me know if any other details are required. > > > > Thanks. > > -- > > > > Nitin Khandelwal > > > > > > -- > Harsh J > -- Nitin Khandelwal
