This patch updat mahout dependency and create 2 profile:
- hadoop1 build mahout with Hadoop 1 dependency (uses by default)
- hadoop2 build mahout with Hadoop 2 dependency
Because if now build mahout and then run it on machine where installed
hadoop 2 - mahout job will be failed.
On Wed, Feb 19, 2014 at 4:21 PM, Sean Owen <[email protected]> wrote:
> Sergey I think it already worked with 2.0, no? (Although it doesn't
> actually use the 2.x APIs). Is this for 2.2 and/or what are the
> high-level changes? I'd imagine mostly packaging stuff.
>
> On Wed, Feb 19, 2014 at 2:14 PM, Sergey Svinarchuk
> <[email protected]> wrote:
> > Today I updated patch in M-1329 to trunk. It's ticket that add support
> > hadoop2 to mahout.
> > I builded mahout with patch and all UT was passed for hadoop1 and
> hadoop2.
> > Also I tested examples/bin on the both hadoop version.
> > Can somebody from committers review patch and test it?
> >
> > Thanks,
> > Sergey!
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
