my take is legacy is just a module (aka maven artifact). Just like it
is now. we just need to re-route(cut) dependencies on it.
On Fri, Mar 6, 2015 at 2:56 PM, Pat Ferrel wrote:
> The simplest way to split the project is into engines—hadoop and spark. What
> is happening with H2O? is it being u
The simplest way to split the project is into engines—hadoop and spark. What is
happening with H2O? is it being used? Flink isn’t anything like ready for a
release.
Again the simplest would be two packaged builds, one for legacy stuff, which
would not require Scala or Spark at all.
The other w
On Fri, Mar 6, 2015 at 1:41 PM, Andrew Palumbo wrote:
>
> On 03/06/2015 12:44 PM, Pat Ferrel wrote:
>
>> This is great.
>>
>> So we’ve talked about a name change and shortly we’ll be forced to come
>> up with something the describes what Mahout has become. Most past users
>> think of it as a scal
On 03/06/2015 12:44 PM, Pat Ferrel wrote:
This is great.
So we’ve talked about a name change and shortly we’ll be forced to come up with
something the describes what Mahout has become. Most past users think of it as
a scalable ML library on Hadoop. That may describe Mahout-Legacy but it seems
This is great.
So we’ve talked about a name change and shortly we’ll be forced to come up with
something the describes what Mahout has become. Most past users think of it as
a scalable ML library on Hadoop. That may describe Mahout-Legacy but it seems
like we need a name for the Scala DSL/Spark
Thanks AP
On Thursday, March 5, 2015, Andrew Palumbo wrote:
> I went through all of the unresolved JIRA issues and marked all with at
> least a "legacy" or "scala". (for lack of a better name for all that is not
> legacy) label. Hopefully I got them all.
>
> Some are labelled with both (math, bu
I went through all of the unresolved JIRA issues and marked all with at
least a "legacy" or "scala". (for lack of a better name for all that is
not legacy) label. Hopefully I got them all.
Some are labelled with both (math, build, documentation related to both
or neither, etc.)
legacy issues
