[
https://issues.apache.org/jira/browse/FLINK-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15482143#comment-15482143
]
Vasia Kalavri commented on FLINK-2254:
--------------------------------------
Hi [~ivan.mushketyk]
thanks a lot for creating the design document!
I agree with [~greghogan] that separate classes might work better than a common
hierarchy. Actually, I don't really see the intuition behind adding the
{{BaseGraph}} interface. What methods would you add there that would be common
to both bipartite and other graphs?
As for the vertex Ids, in the general case those might be different. Think e.g.
movie-actor graphs or user-tweet graphs. If it simplifies the design, we could
initially have a first implementation with the same id type for top and bottom
vertices and use a label to distinguish them instead. Let me know what you both
think.
> 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)
