hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sarthak Dudhara <sarthak...@gmail.com>
Subject Re: JobClient equivalent in new mapreduce api
Date Mon, 10 Jan 2011 17:21:02 GMT
ok. sure. Thats useful. I will try that out.

Sarthak Dudhara



On Sun, Jan 9, 2011 at 10:25 AM, Harsh J <qwertymaniac@gmail.com> wrote:

> On Sun, Jan 9, 2011 at 10:57 PM, Sarthak Dudhara <sarthak.83@gmail.com>
> wrote:
> > Hi Harsh,
> > Thanks for the reply...
> > I am currently using the job.submit(). Is there a way to track the job
> > status with that using the API? I thought JobClient used to provide that.
> >
> > What can I use from my application to query the state of the jobs that
> were
> > submitted using the job.submit()?
>
> Hm, I think you can somehow use the JobClient to fetch states for any
> given JobID. You'd have to downgrade the newer JobID to the older
> JobID (Using older JobID.downgrade(Newer JobID)) before you use it. It
> should work, try it with JobClient.getJob() and let us know.
>
> > I found the ClusterStatus class in 0.20.2 but not Cluster which is in
> 0.21.
>
> Ah yes, Cluster is a 0.21 class. I did not know you were on 0.20.
>
> > The problem I am facing is that I used the new APIs in the mapreduce
> package
> > instead of the mapred package. I didnt know that it was incomplete. I
> guess
> > the old APIs should not be marked deprecated as it misguides users to not
> > use it.
>
> The deprecated API will not be marked so in the 0.20.3 release coming
> soon, and should be okay to use in 0.20.2 itself; ignoring most
> deprecation warnings in mapreduce. This change has already been
> committed to the 0.20 branch.
>
> --
> Harsh J
> www.harshj.com
>

Mime
View raw message