[
https://issues.apache.org/jira/browse/FLINK-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468506#comment-15468506
]
Ivan Mushketyk commented on FLINK-2254:
---------------------------------------
Hi Greg. Thank you for your comment.
Could you please elaborate why there is a need for a BipartiateEdge class? Will
vertices DataSets have different id types?
I would like to read [~vkalavri] feedback, but I think there are pros and cons
of both solutions. Common hierarchy can help to reuse some code, but with
separate classes we can have cleaner interfaces.
I we will go with different classes, we can add methods:
topProjection() and bottomProjection() that will convert bipartite graph into a
one-mode Graph to bridge the gap between two types.
> Add Bipartite Graph Support for Gelly
> -------------------------------------
>
> Key: FLINK-2254
> URL: https://issues.apache.org/jira/browse/FLINK-2254
> Project: Flink
> Issue Type: New Feature
> Components: Gelly
> Affects Versions: 0.10.0
> Reporter: Andra Lungu
> Assignee: Ivan Mushketyk
> Labels: requires-design-doc
>
> A bipartite graph is a graph for which the set of vertices can be divided
> into two disjoint sets such that each edge having a source vertex in the
> first set, will have a target vertex in the second set. We would like to
> support efficient operations for this type of graphs along with a set of
> metrics(http://jponnela.com/web_documents/twomode.pdf).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
