mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Fwd: Moving to new Hadoop APIs
Date Tue, 25 May 2010 19:45:45 GMT
I presume that Robin's rework addresses this, right?

---------- Forwarded message ----------
From: Chris K Wensel <chris@wensel.net>
Date: Tue, May 25, 2010 at 12:43 PM
Subject: Re: Moving to new Hadoop APIs
To: Ted Dunning <ted.dunning@gmail.com>


you guys need to update the mail list page. still sends to lucene.apache.org

On May 25, 2010, at 12:40 PM, Ted Dunning wrote:


Thanks.

On Tue, May 25, 2010 at 12:20 PM, Chris K Wensel <chris@wensel.net> wrote:

> I'm not on the list.
>
> here is my opinion on the new apis
>
> http://groups.google.com/group/cascading-user/browse_thread/thread/4dc26b68401bbc0f#
>
> and here
>
> http://stackoverflow.com/questions/2855167/which-hadoop-api-version-should-i-use/2859863#2859863
>
> I can reply to the list, but am rushing out of the office. let me know.
>
> ckw
>
> On May 25, 2010, at 11:45 AM, Ted Dunning wrote:
>
>
> Chris,
>
> Can you comment on this?
>
> ---------- Forwarded message ----------
> From: Sean Owen <srowen@gmail.com>
> Date: Tue, May 25, 2010 at 11:37 AM
> Subject: Re: Moving to new Hadoop APIs
> To: Mahout Dev List <dev@mahout.apache.org>, Ankur Goel <
> ankur_goel79@yahoo.com>
>
>
> First snag I've hit -- the new APIs don't include an equivalent of
> MultipleInputs, which is the primary support for mapping several input
> paths. Anyone happen to know the equivalent (esp. Ankur)? This could
> be a bear to reproduce on our own.
>
> Sean
>
> On Tue, May 25, 2010 at 3:17 PM, Sean Owen <srowen@gmail.com> wrote:
> > Just to state what seems to be in progress -- looks like we are agreed
> > we should move to the new Hadoop APIs. Some code is already using it;
> > most of the part that isn't is the recommender which was due to some
> > strange bugs deep in Hadoop in prior versions. It's time to try it
> > again. I'm going to work on porting everything forward now.
> >
> > The other argument against this was that Amazon EMR runs 0.18.3. I
> > think Jeff already established that what we're doing has already
> > broken compatibility with 0.18.x. We can point those users to release
> > 0.3 and say they can try to back-port that code to 0.18.x
> > compatibility. But 0.4 onwards is for 0.20.x+ and you can run your own
> > cluster using AWS and hopefully EMR updates soon.
> >
> > Sean
> >
>
>
>  --
> Chris K Wensel
> chris@concurrentinc.com
> http://www.concurrentinc.com
>
>

  --
Chris K Wensel
chris@concurrentinc.com
http://www.concurrentinc.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message