I prefer the latter(MultipleOutputFormat) as I would not have had to
change my code.
Everything would have stayed in the outputformat. And I hardly need
the extra features.
Oh well, got to keep with the times.
On Tue, Oct 26, 2010 at 2:44 AM, Rekha Joshi <[EMAIL PROTECTED]> wrote:
> Hi Saptarshi,
> AFAIK, this is an intermediate stage where the old api is supported, while
> evolving the new api.
> In 0.21, the old api - MultipleOutputFormat is not deprecated.
> http://hadoop.apache.org/mapreduce/docs/r0.21.0/api/index.html.In future it
> might be.
> From usage perspective, what MultipleOutputs allows is not possible via
> MultipleOutputFormat.With MultipleOutputs in map one can have reduce phase,
> can have different formats of output..
> So what you need should be the deciding factor. And ofcourse, a wary user is
> a smart user!
> Thanks & Regards,
> On 10/26/10 12:05 PM, "Saptarshi Guha" <[EMAIL PROTECTED]> wrote:
> I notice in 0.21 there is org.apache.hadoop.mapreduce.lib.output
> MultipleOutputs and in
> 0.20.1 there is org.apache.hadoop.mapred.lib MultipleOutputFormat .
> Going forward, will the latter be deprecated? Which is better to use?
> I prefer the latter but
> since it isn't in o.a.h.mapreduce i'm wary it might be discontinued.