Github user mallman commented on the issue:
https://github.com/apache/spark/pull/15125
> I feel like i really don't know anything about graphx and can't evaluate
this. It seems reasonable. I don't know if graphx is really active at this
stage?
Understood. Let me respond to your concerns.
First, this PR has undergone extensive review and revision from people who
have experience with this codebase, including from someone (me) who's
successfully scaled it to a pregel computation with 800+ iterations. Without
this patch, that computation is impossible. I'm not a committer, but as someone
who's spent a large amount of time in the guts of GraphX I believe I'm
qualified to sign off on this PR.
Second, the consumers of the GraphX codebase are dependent on support of
it. I understand if the Spark team doesn't want to support it anymore, but in
that case I think the responsible thing to do would be to split it out and put
it into its own repo. That would allow the interested parties to maintain it
independently of Spark. So long as GraphX is part of Spark, the only way to
maintain it is through the Spark project.
There seems to be some sentiment that GraphX is somehow deprecated or a
dead end project, yet I do not see a viable alternative. Even then, it would be
very helpful to _officially_ deprecate the project before ending support of it.
Thanks.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
