Mailing-List: contact dev-help@mahout.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mahout.apache.org
Received-SPF: pass (athena.apache.org: domain of jake.mannix@gmail.com
 designates 209.85.213.42 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=tUJrLJqamGSkxUjJfVO3ZVYEk7NDcc6p8vjj0ImXpbMAFmmPftvVEU+0Kz4mSNkOUs
         xjrogNtxhtKBjs6bkxD4Pp0Gkgv0SbD0zGZCXqzHE2KBS8norXr2qoSZc3pjroZ2RrmA
         +wc1KrxBswlIQsO+pm7GhYt8LW0pUARHg5cZQ=
MIME-Version: 1.0
In-Reply-To: <BANLkTikJius=ZcDrg_hD8c6Dk2dfdsdMfw@mail.gmail.com>
References: <22899832.226481288819585141.JavaMail.jira@thor>
 <1509164319.32996.1305971567849.JavaMail.tomcat@hel.zones.apache.org>
 <BANLkTinqmrxbsxa-rvhiPdKep4kyrp+q=Q@mail.gmail.com>
 <BANLkTimK2KFAM8sqYF_AkLM4whwLtpG+Rg@mail.gmail.com>
 <BANLkTimH1UUSOz75SwabJifwFSA+sr6xjg@mail.gmail.com>
 <BANLkTimROZzSK_jmp880WgydQEK5wyvFcQ@mail.gmail.com>
 <5532208F-13E8-4CA1-8E8B-FC98D9C07F10@apache.org>
 <BANLkTinuWcaRRX29MGTQ4cLbjfS=rU0S_A@mail.gmail.com>
 <4DD96214.8020801@gatech.edu>
 <BANLkTikJius=ZcDrg_hD8c6Dk2dfdsdMfw@mail.gmail.com>
From: Jake Mannix <jake.mannix@gmail.com>
Date: Sun, 22 May 2011 13:41:22 -0700
Message-ID: <BANLkTikHPhjey1873_qAJH0nG1SGYJzx6A@mail.gmail.com>
Subject: Re: [jira] [Commented] (MAHOUT-537) Bring DistributedRowMatrix into
 compliance with Hadoop 0.20.2
To: dev@mahout.apache.org
Content-Type: multipart/alternative; boundary=20cf303dd266f4ecce04a3e361c4

--20cf303dd266f4ecce04a3e361c4
Content-Type: text/plain; charset=ISO-8859-1

On Sun, May 22, 2011 at 12:35 PM, Sean Owen <srowen@gmail.com> wrote:

> I think you'll have to push that for 1.0 for now then; 0.20.x doesn't
> have map-side joins. Yes that is a blocker for what you're trying to
> do and what Sebastian is trying to do for recommendations. I've
> already reimplemented recommenders separately with these things and it
> simplifies and speeds up the pipeline.
>

Wait, are you saying that we should force things like matrix multiplication
to become a 3-job process, instead of the current 1-job process?

I thought we've already discussed and decided that moving to 0.20 APIs
where possible should be done, but where it removes functionality and
efficiency, we would allow the old API?

  -jake

--20cf303dd266f4ecce04a3e361c4--