Github user mallman commented on the issue:
https://github.com/apache/spark/pull/15125
> Yeah, catch-22. I'd also like to split out graphx, but I sorta think
that's what's already happened with GraphFrames. I don't feel strongly enough
to campaign for it, but think graphx should probably be deprecated soon.
Unfortunately, GraphFrames does not currently scale to the level we need.
Because of fundamental differences between RDDs and DataFrames in the way they
can be extended, I do not see that changing anytime soon. For those reasons,
GraphX remains essential to large-scale consumers. But certainly I'm all for
splitting it out into its own repo if it means the community can better
maintain it.
Right now we're keeping some patches on our own private branch, but since
there's community interest in this patch (small as it may be) and a significant
amount of work done on this PR, I hope we can merge this in.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
