You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-user@hadoop.apache.org by Ivan Balashov <ib...@iponweb.net> on 2013/09/17 01:34:10 UTC
mapred.join package not migrated to mapreduce
Hi,
Just wondering if there is any particular reason that 'mapred.join' package
never found its way into 'mapreduce'. Being in the old space makes its use
rather inconvenient when most of its former neighbors now happily live in
the new package.
Is this package recommended for prod at all, or maybe, there is an
alternative?
Thanks,
--
Ivan Balashov
Re: mapred.join package not migrated to mapreduce
Posted by kun yan <ya...@gmail.com>.
mapred is not recommended for use I understand mapred is based
interface, but mapreduce is based on an abstract class
2013/9/17 Ivan Balashov <ib...@iponweb.net>
> Hi,
>
> Just wondering if there is any particular reason that 'mapred.join'
> package never found its way into 'mapreduce'. Being in the old space makes
> its use rather inconvenient when most of its former neighbors now happily
> live in the new package.
>
> Is this package recommended for prod at all, or maybe, there is an
> alternative?
>
> Thanks,
>
> --
> Ivan Balashov
>
--
In the Hadoop world, I am just a novice, explore the entire Hadoop
ecosystem, I hope one day I can contribute their own code
YanBit
yankunhadoop@gmail.com
Re: mapred.join package not migrated to mapreduce
Posted by Chris Douglas <cd...@apache.org>.
Amareshwari ported this in MAPREDUCE-355:
https://issues.apache.org/jira/browse/MAPREDUCE-355
It has not been backported to the 1.x line, but it is in the 2.x branch. -C
On Mon, Sep 16, 2013 at 4:34 PM, Ivan Balashov <ib...@iponweb.net> wrote:
> Hi,
>
> Just wondering if there is any particular reason that 'mapred.join' package
> never found its way into 'mapreduce'. Being in the old space makes its use
> rather inconvenient when most of its former neighbors now happily live in
> the new package.
>
> Is this package recommended for prod at all, or maybe, there is an
> alternative?
>
> Thanks,
>
> --
> Ivan Balashov
Re: mapred.join package not migrated to mapreduce
Posted by kun yan <ya...@gmail.com>.
mapred is not recommended for use I understand mapred is based
interface, but mapreduce is based on an abstract class
2013/9/17 Ivan Balashov <ib...@iponweb.net>
> Hi,
>
> Just wondering if there is any particular reason that 'mapred.join'
> package never found its way into 'mapreduce'. Being in the old space makes
> its use rather inconvenient when most of its former neighbors now happily
> live in the new package.
>
> Is this package recommended for prod at all, or maybe, there is an
> alternative?
>
> Thanks,
>
> --
> Ivan Balashov
>
--
In the Hadoop world, I am just a novice, explore the entire Hadoop
ecosystem, I hope one day I can contribute their own code
YanBit
yankunhadoop@gmail.com
Re: mapred.join package not migrated to mapreduce
Posted by kun yan <ya...@gmail.com>.
mapred is not recommended for use I understand mapred is based
interface, but mapreduce is based on an abstract class
2013/9/17 Ivan Balashov <ib...@iponweb.net>
> Hi,
>
> Just wondering if there is any particular reason that 'mapred.join'
> package never found its way into 'mapreduce'. Being in the old space makes
> its use rather inconvenient when most of its former neighbors now happily
> live in the new package.
>
> Is this package recommended for prod at all, or maybe, there is an
> alternative?
>
> Thanks,
>
> --
> Ivan Balashov
>
--
In the Hadoop world, I am just a novice, explore the entire Hadoop
ecosystem, I hope one day I can contribute their own code
YanBit
yankunhadoop@gmail.com
Re: mapred.join package not migrated to mapreduce
Posted by Chris Douglas <cd...@apache.org>.
Amareshwari ported this in MAPREDUCE-355:
https://issues.apache.org/jira/browse/MAPREDUCE-355
It has not been backported to the 1.x line, but it is in the 2.x branch. -C
On Mon, Sep 16, 2013 at 4:34 PM, Ivan Balashov <ib...@iponweb.net> wrote:
> Hi,
>
> Just wondering if there is any particular reason that 'mapred.join' package
> never found its way into 'mapreduce'. Being in the old space makes its use
> rather inconvenient when most of its former neighbors now happily live in
> the new package.
>
> Is this package recommended for prod at all, or maybe, there is an
> alternative?
>
> Thanks,
>
> --
> Ivan Balashov
Re: mapred.join package not migrated to mapreduce
Posted by kun yan <ya...@gmail.com>.
mapred is not recommended for use I understand mapred is based
interface, but mapreduce is based on an abstract class
2013/9/17 Ivan Balashov <ib...@iponweb.net>
> Hi,
>
> Just wondering if there is any particular reason that 'mapred.join'
> package never found its way into 'mapreduce'. Being in the old space makes
> its use rather inconvenient when most of its former neighbors now happily
> live in the new package.
>
> Is this package recommended for prod at all, or maybe, there is an
> alternative?
>
> Thanks,
>
> --
> Ivan Balashov
>
--
In the Hadoop world, I am just a novice, explore the entire Hadoop
ecosystem, I hope one day I can contribute their own code
YanBit
yankunhadoop@gmail.com
Re: mapred.join package not migrated to mapreduce
Posted by Chris Douglas <cd...@apache.org>.
Amareshwari ported this in MAPREDUCE-355:
https://issues.apache.org/jira/browse/MAPREDUCE-355
It has not been backported to the 1.x line, but it is in the 2.x branch. -C
On Mon, Sep 16, 2013 at 4:34 PM, Ivan Balashov <ib...@iponweb.net> wrote:
> Hi,
>
> Just wondering if there is any particular reason that 'mapred.join' package
> never found its way into 'mapreduce'. Being in the old space makes its use
> rather inconvenient when most of its former neighbors now happily live in
> the new package.
>
> Is this package recommended for prod at all, or maybe, there is an
> alternative?
>
> Thanks,
>
> --
> Ivan Balashov
Re: mapred.join package not migrated to mapreduce
Posted by Chris Douglas <cd...@apache.org>.
Amareshwari ported this in MAPREDUCE-355:
https://issues.apache.org/jira/browse/MAPREDUCE-355
It has not been backported to the 1.x line, but it is in the 2.x branch. -C
On Mon, Sep 16, 2013 at 4:34 PM, Ivan Balashov <ib...@iponweb.net> wrote:
> Hi,
>
> Just wondering if there is any particular reason that 'mapred.join' package
> never found its way into 'mapreduce'. Being in the old space makes its use
> rather inconvenient when most of its former neighbors now happily live in
> the new package.
>
> Is this package recommended for prod at all, or maybe, there is an
> alternative?
>
> Thanks,
>
> --
> Ivan Balashov