Most of the inquiries I've had about Gelly in recent memory have been from folks looking for a streaming solution, and it's only been a handful.
+1 for dropping Gelly David On Mon, Jan 3, 2022 at 2:41 PM Till Rohrmann <trohrm...@apache.org> wrote: > I haven't seen any changes or requests to/for Gelly in ages. Hence, I > would assume that it is not really used and can be removed. > > +1 for dropping Gelly. > > Cheers, > Till > > On Mon, Jan 3, 2022 at 2:20 PM Martijn Visser <mart...@ververica.com> > wrote: > >> Hi everyone, >> >> Flink is bundled with Gelly, a Graph API library [1]. This has been >> marked as approaching end-of-life for quite some time [2]. >> >> Gelly is built on top of Flink's DataSet API, which is deprecated and >> slowly being phased out [3]. It only works on batch jobs. Based on the >> activity in the Dev and User mailing lists, I don't see a lot of questions >> popping up regarding the usage of Gelly. Removing Gelly would reduce CI >> time and resources because we won't need to run tests for this anymore. >> >> I'm cross-posting this to the User mailing list to see if there are any >> users of Gelly at the moment. >> >> Let me know your thoughts. >> >> Martijn Visser | Product Manager >> >> mart...@ververica.com >> >> >> [1] >> https://nightlies.apache.org/flink/flink-docs-stable/docs/libs/gelly/overview/ >> >> [2] https://flink.apache.org/roadmap.html >> >> [3] https://lists.apache.org/thread/b2y3xx3thbcbtzdphoct5wvzwogs9sqz >> >> <https://www.ververica.com/> >> >> >> Follow us @VervericaData >> >> -- >> >> Join Flink Forward <https://flink-forward.org/> - The Apache Flink >> Conference >> >> Stream Processing | Event Driven | Real Time >> >>
