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 ted.dunning@gmail.com
 designates 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPud8TqvBzzXvcBpvCoO9V1VzSSc+C+QrMzdKh75=hVB8XBHMQ@mail.gmail.com>
References: <534ABF21.9000906@apache.org>
 <CAPud8TqvBzzXvcBpvCoO9V1VzSSc+C+QrMzdKh75=hVB8XBHMQ@mail.gmail.com>
From: Ted Dunning <ted.dunning@gmail.com>
Date: Sun, 13 Apr 2014 10:20:07 -0700
Message-ID: 
 <CAJwFCa0DyjqUH_rhViGbvuFpjO=1=rqrF0SV462cE7J1CB0i1w@mail.gmail.com>
Subject: Re: Tackling the "legacy dilemma"
To: Mahout Dev List <dev@mahout.apache.org>
Content-Type: multipart/alternative; boundary=20cf301d3d7e0b76d104f6efc950

--20cf301d3d7e0b76d104f6efc950
Content-Type: text/plain; charset=UTF-8

On Sun, Apr 13, 2014 at 10:16 AM, Dmitriy Lyubimov <dlieu.7@gmail.com>wrote:

> >  * move the MR algorithms into a separate maven module
> You mean, move  them out  of mahout-core? So the core is for single machine
> stuff only? Plus utils? We probably need to refactor core so there's no
> core at all it seems. Our core, realistically, is utils, mahout-math &
> math-scala(aka scalabindings), engine-agnostic logical layer of
> mahout-spark. But for obvious reasons we probably dont want to put all that
> in a single module. Maybe at some point later when these things become more
> mainstream.


This might be viewed as renaming core to be "mr-legacy" and then pulling
those items we really need out of that.  Math is already separate as are
scala bindings and similar.

--20cf301d3d7e0b76d104f6efc950--