[
https://issues.apache.org/jira/browse/SPARK-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990575#comment-14990575
]
Sean Owen commented on SPARK-3789:
----------------------------------
I'll be quiet now; I like my opinions but I dragged this off-topic. I am really
glad to see Ankur weigh in and say there is more in store for GraphX, and can
look at these changes, and that it's certainly not going away. (I'm reminded
that, actually, MLlib uses it.) We can only gain from having more tools
available in more languages. If we have people to contribute and people to
shepherd / maintain, then a Python API is a no-brainer. I agree that there is a
chicken-and-egg issue: making tools unlocks demand which drives more tools.
Even if one agreed this was a niche application so far, well, it's only niche
until it isn't right?
> [GRAPHX] Python bindings for GraphX
> -----------------------------------
>
> Key: SPARK-3789
> URL: https://issues.apache.org/jira/browse/SPARK-3789
> Project: Spark
> Issue Type: New Feature
> Components: GraphX, PySpark
> Reporter: Ameet Talwalkar
> Assignee: Kushal Datta
> Attachments: PyGraphX_design_doc.pdf
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
