[
https://issues.apache.org/jira/browse/FLINK-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973972#comment-14973972
]
Vasia Kalavri commented on FLINK-2905:
--------------------------------------
Hi [~mju],
several {{Graph}} methods use the composite {{sourceID - targetID}} key as a
unique identifier. I see the problem with that in your example. If G1 has the
edge 1,3,13 and G2 has the edge 1,3,14, these will match, but what should the
value be in the intersection?
>From the options you present, Option 3 seems the most intuitive to me.
>Alternatively, we could maybe provide an option to the method, defining
>whether the edge value should be used for matching?
> Add intersect method to Graph class
> -----------------------------------
>
> Key: FLINK-2905
> URL: https://issues.apache.org/jira/browse/FLINK-2905
> Project: Flink
> Issue Type: New Feature
> Components: Gelly
> Affects Versions: 0.10
> Reporter: Martin Junghanns
> Assignee: Martin Junghanns
> Priority: Minor
>
> Currently, the Gelly Graph supports the set operations
> {{Graph.union(otherGraph)}} and {{Graph.difference(otherGraph)}}. It would be
> nice to have a {{Graph.intersect(otherGraph)}} method, where the resulting
> graph contains all vertices and edges contained in both input graphs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
