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

In my experience, the chief advantage of GraphX over GraphFrames is the ability to represent vertex state with more sophisticated data structures (supporting more complicated operations) than can be readily represented using a columnar structure. GraphFrames is typically more efficient for data tha

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

Graph processing is tricky. I don’t plan on using GraphX directly, but GraphFrames uses it in its implementation. On Mon, Oct 7, 2024 at 7:07 PM Richard Eggert wrote: > In my experience, the chief advantage of GraphX over GraphFrames is the > ability to represent vertex state with more sophistic

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

That’s awesome! 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: h

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

I’ll organize a hackathon. A friend wants to finish the implementation of Lucian modularity for GraphFrames. I’ll fix some GraphX bugs at it. I did just blog all about the motif matching in GraphFrames: https://blog.graphlet.ai/financial-crime-and-corruption-network-motifs-4cf2e8e10eb5 Russ On M

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

So this discuss thread and the vote thread to deprecate to leave the option of removing it during 4.X are probably the highest profile it’s been in years. In the past for parts of Spark I’ve cared about I’ve organized virtual meetings to co-ordinate work — if your connected with some of the Spark+

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

I’ll look for a bug to fix. If GraphX is outside of Spark, Spark would tend to break GraphFrames and it will be burdensome on an external project to keep up. Graph computing on Spark is implrtant to a lot of people, is there a way to raise visibility here? On Mon, Oct 7, 2024 at 4:24 PM Holden Kar

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

There are no specific tickets associated with the lack of maintaince or this as the component has not been maintained for a sufficiently long time. If your interested in taking it on that’s wonderful, probably starting with fixing some bugs could be a great place to start and figure out if it’s som

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

I volunteer to maintain GraphX to keep GraphFrames a viable project. I don’t have a clear view on whether it works with Spark 4 or if it needs updates? I don’t have Spark commits but I’m a committer on Apache DataFu and mentored the Spark feature for it. Can someone tell me what is involved? Point

Re: kubeflow spark-operator - error in querying strimzi kafka using structured streaming

Hi Karan, It seems that the way you tried to integrate with GCP is not the way that Kubeflow proposes. They set another way to use the secret for some reason... Here you can see how they tell you to do that. HTH, Nimrod O

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

Hello, We rely on GraphX for an important component of our product. And we really want it to stay a typed interface. Please keep GraphX. Erik From: Holden Karau Date: Sunday, October 6, 2024 at 06:22 To: Ángel Cc: Russell Jurney , Mich Talebzadeh , Spark dev list , user @spark Subject: Re: