The VOTE is now closed and I believe it passes*, albeit with notable dissent.
The votes are: +1: Mich Talebzadeh Dongjoon Hyun LC Hsieh Sean Owen Jungtaek Lim Mridul Muralidharan Yang Jie beliefer Wenchen Fan Denny Lee Hyukjin Kwon Herman van Hovell 0s: -1: Mark Hamstra Ángel While not on the VOTE thread it’s self there are ~two user on the user list who asked that it not be deprecated and one on the DISCUSS thread who offered to take on maintaining it. Given the dissent I think that we should update the docs to include a message: GraphX is not currently maintained and if maintainers are not found may be removed in future minor versions (deprecated). If you are interested in helping maintain GraphX please reach out on the developer mailing list. We recommend exploring GraphFrames or openCypher on Spark as potential migration targets. I hope this course of action seems like a reasonable balancing of folks views. While it’s possible that we un-deprecate GraphX I think having the reality of the current state of GraphX communicated as we go into 4.0 gives us much needed freedom for any future decisions we make here. If any committer is willing to step-forward to be a mentor I think the chance of growing new maintainers here is much higher. * I _believe_ that since it is not strictly a code change the -1 is not a veto. If there is disagreement here happy to discuss that on private@. On a personal note I would like us to see this not as a failing on part of the project but rather a healthy activity allowing us set user expectations more clearly. Twitter: https://twitter.com/holdenkarau Fight Health Insurance: https://www.fighthealthinsurance.com/ <https://www.fighthealthinsurance.com/?q=hk_email> Books (Learning Spark, High Performance Spark, etc.): https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> YouTube Live Streams: https://www.youtube.com/user/holdenkarau Pronouns: she/her On Fri, Oct 4, 2024 at 2:57 PM Mark Hamstra <markhams...@gmail.com> wrote: > -1(*) reasoning posted in the DISCUSS thread > > On Mon, Sep 30, 2024 at 12:40 PM Holden Karau <holden.ka...@gmail.com> > wrote: > > > > I think it has been de-facto deprecated, we haven’t updated it > meaningfully in several years. I think removing the API would be excessive > but deprecating it would give us the flexibility to remove it in the not > too distant future. > > > > That being said this is not a vote to remove GraphX, I think that > whenever that time comes (if it does) we should have a separate vote > > > > This VOTE will be open for a little more than one week, ending on > October 8th*. To vote reply with: > > +1 Deprecate GraphX > > 0 I’m indifferent > > -1 Don’t deprecate GraphX because ABC > > > > If you have a binding vote to simplify you tallying at the end please > mark your vote with a *. > > > > (*mostly because I’m going camping for my birthday) > > > > Twitter: https://twitter.com/holdenkarau > > Fight Health Insurance: https://www.fighthealthinsurance.com/ > > Books (Learning Spark, High Performance Spark, etc.): > https://amzn.to/2MaRAG9 > > YouTube Live Streams: https://www.youtube.com/user/holdenkarau > > Pronouns: she/her > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
