Re: [DISCUSS] Deprecate GraphX OR Find new maintainers interested in GraphX OR leave it as is?

So are there companies using it? And are they willing to contribute to maintaining it? Twitter: https://twitter.com/holdenkarau Fight Health Insurance: https://www.fighthealthinsurance.com/ Books (Learning Spark, High Performance Spark, etc.): htt

Re: [DISCUSS] Deprecate GraphX OR Find new maintainers interested in GraphX OR leave it as is?

That would definitely affect companies using GraphX, but at least they’d have the choice to migrate their code. I think that’s probably the way to go. El dom, 6 oct 2024 a las 6:09, Holden Karau () escribió: > So removing GraphX from Spark would not prevent GraphFrames from > continuing, they co

Re: [DISCUSS] Deprecate GraphX OR Find new maintainers interested in GraphX OR leave it as is?

So removing GraphX from Spark would not prevent GraphFrames from continuing, they could pick up the GraphX source and incorporate it into their project. Twitter: https://twitter.com/holdenkarau Fight Health Insurance: https://www.fighthealthinsurance.com/

Re: [DISCUSS] Deprecate GraphX OR Find new maintainers interested in GraphX OR leave it as is?

A lot of people like me use GraphFrames for its connected components implementation and its motif matching feature. I am willing to work on it to keep it alive. They did a 0.8.3 release not too long ago. Please keep GraphX alive. On Sat, Oct 5, 2024 at 3:44 PM Mich Talebzadeh wrote: > I added th

Re: [DISCUSS] Deprecate GraphX OR Find new maintainers interested in GraphX OR leave it as is?

I added the user list as they may have vested interest here and and hopefully can contribute Few suggestions: 1. Data-Driven Decision Making: Return to the core metrics—analyze usage trends, performance benchmarks, and the actual impact on businesses that rely on GraphX. Objectivity can