I was thinking, if its a thing we want to pursue, let's maybe attempt some initial stabs- perhaps start a branch, and get a feel for how scary of a nightmare its going to be. Then we can start talking time tables.
In my mind it will either be 1- Crazy easy, just creating a distributed context for the streaming context and everything else kind of falls into place 2- crazy hard- nearly reinventing the wheel 3- some mixture of the two. The upshot with the imminent GPU acceleration: we'd be the first streaming + gpu which would be quite dope Trevor Grant Data Scientist https://github.com/rawkintrevo http://stackexchange.com/users/3002022/rawkintrevo http://trevorgrant.org *"Fortunate is he, who is able to know the causes of things." -Virgil* On Fri, Dec 9, 2016 at 10:52 AM, Andrew Palumbo <[email protected]> wrote: > It's that this is something that we've been talking about for a while... > would you be thinking for before 1.0 or after 1.0? > > > Sent from my Verizon Wireless 4G LTE smartphone > > > -------- Original message -------- > From: Trevor Grant <[email protected]> > Date: 12/09/2016 8:05 AM (GMT-08:00) > To: [email protected] > Subject: [DISCUSS] Mahout Streaming Bindings > > Wanted to kick off a discussion about if we're ready to start thinking > about coming up with some bindings for streaming engines. > > Had a question at a meetup tuesday in seattle, and it got me thinking about > it. > > In my mind they would be a discreet set of Bindings, Flink Streaming > /Spark Streaming / (Beam?) / etc > > I have some fleeting thoughts, but didn't write any of the bindings and > have only attempted to grok them in passing. > > Or maybe not something we want to pursue at this time? However, it is > something I'd be interested in tinkering with on a branch of my own... > > tg > > Trevor Grant > Data Scientist > https://github.com/rawkintrevo > http://stackexchange.com/users/3002022/rawkintrevo > http://trevorgrant.org > > *"Fortunate is he, who is able to know the causes of things." -Virgil* >
