[
https://issues.apache.org/jira/browse/FLINK-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15483350#comment-15483350
]
Ivan Mushketyk commented on FLINK-2254:
---------------------------------------
Hi Vasia,
Thank you for reviewing the design doc.
I do agree with you and Greg, it seems cleaner to keep these classes separate.
Regarding common methods, I was thinking about methods like map verticies or
map edges.
If we agree that bipartite graph should be a separate classes I will add
subtasks for this task (this task seems too big) like:
Add BipartiteGraph class
Implement BipartiteGraph reader
Implement bipartite graph generators
Implement bipartite graph stats
For the bipartite graph I'll implement methods for accessing edges and
verticies and projections.
What do you think about this?
> 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)
