Great, thank you Theodore! @Stavros Let me know when you need edit permissions to add the FLIP to the wiki.
Cheers, Fabian 2017-07-06 2:33 GMT+02:00 Theodore Vasiloudis < theodoros.vasilou...@gmail.com>: > Hello all, > > I just wanted to indicate that I would be very willing to help out with > code reviews > for this project and participating in design discussions. > > But I should note that I don' think I'll have time to contribute code until > I get back to Stockholm in September. > > Regards, > Theodore > > On Tue, Jul 4, 2017 at 9:41 AM, Andrea Spina <andrea.sp...@radicalbit.io> > wrote: > > > Hi all, > > yes, we did too. We - from Radicalbit - have submitted a talk focused > > on the recently released flink-jpmml library about model serving. > > Lately, it became part of the FlinkML project. > > > > Cheers, Andrea > > > > 2017-07-04 16:14 GMT+02:00 Boris Lublinsky < > boris.lublin...@lightbend.com > > >: > > > Yes, > > > I submitted a talk with Stavros on model serving > > > > > > > > > Boris Lublinsky > > > FDP Architect > > > boris.lublin...@lightbend.com > > > https://www.lightbend.com/ > > > > > > On Jul 3, 2017, at 1:18 PM, Robert Metzger <rmetz...@apache.org> > wrote: > > > > > > Big +1 from my side on getting this effort started. > > > > > > Users have asked for this and I would like to see some progress there. > > > Did anybody submit a talk about the ML efforts to Flink Forward Berlin > > this > > > year? > > > > > > On Fri, Jun 30, 2017 at 6:04 PM, Fabian Hueske <fhue...@gmail.com> > > wrote: > > >> > > >> Yes, I know that Theo is engaged in the ML efforts but wasn't sure how > > >> much > > >> he is involved in the model serving part (thought he was more into the > > >> online learning part). > > >> It would be great if Theo could help here! > > >> > > >> I just wanted to make sure that we find somebody to help > bootstrapping. > > >> > > >> Cheers, Fabian > > >> > > >> > > >> 2017-06-30 17:52 GMT+02:00 Stavros Kontopoulos < > > st.kontopou...@gmail.com>: > > >> > > >> > Hi Fabian, > > >> > > > >> > However, we should keep in mind that we need a committer to > bootstrap > > >> > the > > >> > > new module. > > >> > > > >> > > > >> > Absolutely I thought Theodore Vassiloudis could help, as an initial > > >> > committer. > > >> > Is this known? He is part of the effort btw. > > >> > > > >> > Best, > > >> > Stavros > > >> > > > >> > On Fri, Jun 30, 2017 at 6:42 PM, Fabian Hueske <fhue...@gmail.com> > > >> > wrote: > > >> > > > >> > > Thanks Stavros (and everybody else involved) for starting this > > effort > > >> > > and > > >> > > bringing the discussion back to the mailing list. > > >> > > > > >> > > As I said before, a model serving module/component would be a > great > > >> > feature > > >> > > for Flink. > > >> > > I see the biggest advantage for such a module in the integration > > with > > >> > > the > > >> > > other APIs and libraries, such as DataStream, CEP, SQL. > > >> > > > > >> > > A FLIP would be a great way to continue your efforts and work on a > > >> > > design > > >> > > for the component. > > >> > > > > >> > > However, we should keep in mind that we need a committer to > > bootstrap > > >> > > the > > >> > > new module. > > >> > > As people are contributing to the model serving module, the number > > of > > >> > > committers should hopefully grow after some time. > > >> > > > > >> > > Best, Fabian > > >> > > > > >> > > 2017-06-30 10:58 GMT+02:00 Stavros Kontopoulos > > >> > > <st.kontopou...@gmail.com > > >> > >: > > >> > > > > >> > > > Hi all, > > >> > > > > > >> > > > After coordinating with Theodore Vasiloudis and the guys behind > > the > > >> > Flink > > >> > > > Model Serving effort (Eron, Radicalbit people, Boris, Bas > (ING)), > > we > > >> > > > propose to start working on the model serving over Flink in a > more > > >> > > official > > >> > > > way. > > >> > > > That translates to capturing design details in a FLIP document. > > >> > > > > > >> > > > Please let's discuss and vote whether you think this FLIP would > be > > >> > > viable. > > >> > > > > > >> > > > Model Serving as a Flink component might involve a lot of work > and > > >> > > > we > > >> > > need > > >> > > > to commit to support it in future Flink releases. > > >> > > > > > >> > > > In the mean time a lot of people have joined Flink ml slack > > channel > > >> > > > ( > > >> > > > https://flinkml.slack.com, https://flinkml-invites. > herokuapp.com/ > > ) > > >> > and I > > >> > > > think its time to try get them gradually on board. > > >> > > > > > >> > > > So far we have several efforts hosted here: > > >> > > > https://github.com/FlinkML > > >> > > > > > >> > > > Related documents for what we are doing: > > >> > > > > > >> > > > Flink ML roadmap > > >> > > > > > >> > > > https://docs.google.com/document/d/ > 1afQbvZBTV15qF3vobVWUjxQc49h3U > > >> > > > d06MIRhahtJ6dw/edit > > >> > > > > > >> > > > Flink MS > > >> > > > > > >> > > > https://docs.google.com/document/d/ > 1CjWL9aLxPrKytKxUF5c3ohs0ickp0 > > >> > > > fdEXPsPYPEywsE/edit# > > >> > > > > > >> > > > PS. I will work on the last document the next few days to > > >> > > > consolidate > > >> > > > effort results to some extend and break work down. > > >> > > > Our target is to provide a generic API based on some plugin > > >> > architecture > > >> > > to > > >> > > > serve different popular models/pipelines along with custom ones > > over > > >> > > flink. > > >> > > > > > >> > > > Best, > > >> > > > Stavros > > >> > > > > > >> > > > > >> > > > > > > > > > > > > >
