Exactly what we're trying to do is scope out that effort, with the goal
of being able to reuse Mahout algos.
Mahout's well-known for it's e.g. recommendation engine; we'd like to
see that (and other algos) leveraged.
So yes, "integrate" with Mahout - and help people already using Mahout
get something better without having to drop Mahout altogether.
Cliff
On 5/1/2014 9:21 AM, Dmitriy Lyubimov wrote:
What i really want to ask you is this. I asked this question before, and
did not get answer. But I assume now you know a bit more about Mahout.
What is your opinion/vision on actually _integrating_ with Mahout?
Integration effort in my definition would be (1) reusing some of Mahout
implementations, and/or (2) helping some of mahout algorithms/components to
do their job better.
What you have been doing to date was something roughly amounting to
building (porting) Mahout (or non-Mahout) algorithms for H20. This, by
definition, is not an integration effort and could happily run forever
without ever requiring a Mahout commit.
I would be interested to hear your thoughts again on what you think it
means to _integrate_ with Mahout.
