Thanks Pat, would love to be included in any smaller group google hangout type discussions.
> Subject: Re: New Mahout Recommender Service > From: [email protected] > Date: Tue, 9 Sep 2014 09:16:04 -0700 > To: [email protected] > > No Jira yet. There are too many moving parts and we’d have to see if it’s > appropriate for Mahout inclusion or as an “example” project. It would be > great to include but we’ll have to see what others think as it takes better > form. All components should be Apache license compatible though. > > I’ll start a Github project. Does anyone object to using this list for > discussion? > > On Sep 9, 2014, at 8:46 AM, Saikat Kanjilal <[email protected]> wrote: > > @Pat Any interest in using http://vertx.io instead of play, have heard some > really good perf stats around this > > We should really start a jira with a list of use cases and then back into a > tech stack and outline the design in jira, thoughts ? > > Sent from my iPhone > > > On Sep 9, 2014, at 8:44 AM, "Martin, Nick" <[email protected]> wrote: > > > > Would absolutely love an ES integration. > > > > -----Original Message----- > > From: Pat Ferrel [mailto:[email protected]] > > Sent: Tuesday, September 09, 2014 10:29 AM > > To: [email protected] > > Subject: New Mahout Recommender Service > > > > Now that we have the basis of several significant improvements to Mahout's > > recommender it seems like we need to go the last step and provide a > > service. Without this it is left to the user to do a lot of integration > > making the current next gen somewhat incomplete. > > > > Using the Hadoop mapreduce code you can get all recs for all people using > > collaborative filtering data or you can use the in-memory single machine > > recommender if you have a small dataset. > > > > The next generation would require Solr or Elasticsearch so why not go the > > extra step and provide a recommender API on top? At very least it would > > give users a single machine API they can call, analogous to the in-memory > > recommender of Mahout 0.9. But it would also be indefinitely scalable. > > > > Is anyone interested in discussing this here? >
