Hi all,
For the successor of the Gelly library, currently in flink-ml we have already
implemented a new iteration framework based on the DataStream API,
which is necessary for a graph processing framework. It could also provide
abilities like allowing for arbitrary states across rounds and asynchronous
iteration that could help implementing more effective graph algorithms.
Thus it looks to me that now we are ready to have a design of the new graph
processing framework based on the unified DataStream API and
replace the Gelly library built on the deprecated DataSet API.
Best,
Yun Gao
[1] https://github.com/apache/flink-ml <https://github.com/apache/flink-ml >
------------------------------------------------------------------
From:Martijn Visser <martijnvis...@apache.org>
Send Time:2022 Oct. 13 (Thu.) 15:52
To:dev <dev@flink.apache.org>
Subject:Re: [VOTE] Drop Gelly
Hi Yu,
The vote is for option 1, remove all code and documentation of Gelly. For
the current users, they can stay on a previous version of Flink which still
contains Gelly. Since Gelly (and the DataSet API) haven't been touched in
multiple releases, there's most likely no need for them to upgrade anyway.
The source code is still available for previous versions, so moving it to
an external repository doesn't seem to add value.
I'm all for it if someone wants to drive a successor: that could be either
done under the ASF Flink umbrella (then I'm looking forwarding to a FLIP)
or of course as their own initiative under flink-extended.
Thanks,
Martijn
On Thu, Oct 13, 2022 at 6:31 AM Yu Li <car...@gmail.com> wrote:
> Hi Martijn,
>
> From the last replies of the previous discussion, I could see there are
> still users using Gelly that expressed their wish to somehow keep this
> module [1] [2] [3]. Therefore, Before giving my vote, I'd like to
> confirm what "Drop Gelly" exactly means. Does it mean that 1) we remove the
> codes and documents of Gelly completely, or 2) just move it out of the main
> repository into a separate one and mark it as EOM (or maybe call for
> maintainers), or 3) something else? And if the #1 option, is there any
> replacement (or any plan)? Thanks.
>
> Best Regards,
> Yu
>
> [1] https://lists.apache.org/thread/4yxb7xnb2070h5lypcd3wxnsck9zwz8f
> <https://lists.apache.org/thread/4yxb7xnb2070h5lypcd3wxnsck9zwz8f >
> [2] https://lists.apache.org/thread/x21p382vjt6nrjnj51fxxtcrp1dqtzyz
> <https://lists.apache.org/thread/x21p382vjt6nrjnj51fxxtcrp1dqtzyz >
> [3] https://lists.apache.org/thread/w2f4yvb75tg5t7g3l7t9z6bvpwmd1t6y
> <https://lists.apache.org/thread/w2f4yvb75tg5t7g3l7t9z6bvpwmd1t6y >
>
>
> On Thu, 13 Oct 2022 at 10:56, Yun Gao <yungao...@aliyun.com.invalid>
> wrote:
>
> > +1
> > Best,
> > Yun Gao
> > ------------------------------------------------------------------
> > From:Martijn Visser <martijnvis...@apache.org>
> > Send Time:2022 Oct. 13 (Thu.) 04:59
> > To:dev <dev@flink.apache.org>
> > Subject:[VOTE] Drop Gelly
> > Hi everyone,
> > I would like to open a vote for dropping Gelly, which was discussed a
> long
> > time ago but never put to a vote [1].
> > Voting will be open for at least 72 hours.
> > Best regards,
> > Martijn
> > https://twitter.com/MartijnVisser82 <https://twitter.com/MartijnVisser82 >
> > https://github.com/MartijnVisser <https://github.com/MartijnVisser >
> > [1] https://lists.apache.org/thread/2m6wtgjvxcogbf9d5q7mqt4ofqjf2ojc
> > <https://lists.apache.org/thread/2m6wtgjvxcogbf9d5q7mqt4ofqjf2ojc >
> >
>
