Hi, Flavio. Indeed, Becket is the best person to answer this question, but as far as I understand the idea is that Alink will be contributed back to Flink in the form of a refactored Flink ML library (sitting on top of the Table API) [1]. You can follow the progress of these efforts by tracking FLIP-39 [2].
[1] https://developpaper.com/why-is-flink-ai-worth-looking-forward-to/ [2] https://cwiki.apache.org/confluence/display/FLINK/FLIP-39+Flink+ML+pipeline+and+ML+libs On Tue, Mar 3, 2020 at 2:02 PM Gary Yao <g...@apache.org> wrote: > Hi Flavio, > > I am looping in Becket (cc'ed) who might be able to answer your question. > > Best, > Gary > > On Tue, Mar 3, 2020 at 12:19 PM Flavio Pompermaier <pomperma...@okkam.it> > wrote: > >> Hi to all, >> since Alink has been open sourced, is there any good reason to keep both >> Flink ML and Alink? >> From what I understood Alink already contains the best ML implementation >> available for Flink..am I wrong? >> Maybe it could make sense to replace the current Flink ML with that of >> Alink..or is that impossible? >> >> Cheers, >> Flavio >> >
