[
https://issues.apache.org/jira/browse/SPARK-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576294#comment-14576294
]
Andy Huang commented on SPARK-7893:
-----------------------------------
I totally agree with u. The reason why we implement union first is that we need
it. But for other ones, if we want to do it more systematically, priorities
should be carefully planed.
> Complex Operators between Graphs
> --------------------------------
>
> Key: SPARK-7893
> URL: https://issues.apache.org/jira/browse/SPARK-7893
> Project: Spark
> Issue Type: Umbrella
> Components: GraphX
> Reporter: Andy Huang
> Labels: complex, graph, join, operators, union
>
> Currently there are 30+ operators in GraphX, while few of them consider
> operators between graphs. The only one is _*mask*_, which takes another graph
> as a parameter and return a new graph.
> In many complex case,such as _*streaming graph, small graph merge into huge
> graph*_, higher level operators of graphs can help users to focus and think
> in graph. Performance optimization can be done internally and be transparent
> to them.
> Complex graph operator list is
> here:[complex_graph_operations|http://techieme.in/complex-graph-operations/]
> * Union of Graphs ( G ∪ H )
> * Intersection of Graphs( G ∩ H)
> * Graph Join
> * Difference of Graphs（G – H）
> * Graph Complement
> * Line Graph ( L(G) )
> This issue will be index of all these operators
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
