>>FWIW the trunk/future-branches have new API MultipleInputs you can
>>pull and include in your project

   Can anyone please tell me how I can do the above thing. How can I use
MultipleInputs of higher hadoop version to use it in lower hadoop version.

Thanks

On Wed, Aug 24, 2011 at 5:50 PM, Harsh J <ha...@cloudera.com> wrote:

> 0.20.x supports the older API and it has been 're-deemed' as the
> stable one. You shouldn't face any hesitation in using it as even 0.23
> would carry it (although there its properly deprecated). This is quite
> some confusion but I guess you still won't have some of the old API
> features in the new one.
>
> FWIW the trunk/future-branches have new API MultipleInputs you can
> pull and include in your project. Also, alternative distributions that
> do stable backports may carry MultipleInputs in the new API (I use
> CDH3 and it does have mapreduce.lib.input.MultipleInputs backported in
> it).
>
> On Wed, Aug 24, 2011 at 2:40 PM, praveenesh kumar <praveen...@gmail.com>
> wrote:
> > Hello guys,
> >
> > I am looking to use MultipleInputs.addInputPath() method in hadoop
> 0.20.2.
> > But when I am looking to its signature in the API, its like this :
> > *
> >          public static void addInputPath(JobConf conf,
> >                                                        Path path,
> >                                                        Class<? extends
> > InputFormat> inputFormatClass)*
> >
> >   *      public static void addInputPath(JobConf conf,
> >                                                       Path path,
> >                                                       Class<? extends
> > InputFormat> inputFormatClass,
> >                                                       Class<? extends
> > Mapper> mapperClass)*
> >
> > But as far as I know in hadoop 0.20.2, JobConf object is deprecated.
> > How can I use MultipleInputs.addInputPath() in hadoop. Is there any other
> > way or any new class introduced instead of this one.
> >
> > Thanks,
> > Praveenesh
> >
>
>
>
> --
> Harsh J
>

Reply via email to