[
https://issues.apache.org/jira/browse/FLINK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691610#comment-15691610
]
Ivan Mushketyk edited comment on FLINK-1536 at 11/23/16 11:11 PM:
------------------------------------------------------------------
Oh, sorry, I didn't mean to type "bipartiate" word there :) Somehow this word
ingrained in my muscle memory after working on the bipartite graph task :)
Anyway. I'll do some background research and come up with a design document.
Regarding a FLIP. Are there any guidlines about how (or even in what case) to
create one?
was (Author: ivan.mushketyk):
Oh, sorry, I didn't mean to type "bipartiate" word there :) Somehow this word
ingrained in my muscle memory after working on bipartite graph task :)
Anyway. I'll do some background research and come up with a design document.
Regarding a FLIP. Are there any guidlines about how (or even when) to create
one?
> Graph partitioning operators for Gelly
> --------------------------------------
>
> Key: FLINK-1536
> URL: https://issues.apache.org/jira/browse/FLINK-1536
> Project: Flink
> Issue Type: New Feature
> Components: Gelly
> Reporter: Vasia Kalavri
> Priority: Minor
>
> Smart graph partitioning can significantly improve the performance and
> scalability of graph analysis applications. Depending on the computation
> pattern, a graph partitioning algorithm divides the graph into (maybe
> overlapping) subgraphs, optimizing some objective. For example, if
> communication is performed across graph edges, one might want to minimize the
> edges that cross from one partition to another.
> The problem of graph partitioning is a well studied problem and several
> algorithms have been proposed in the literature. The goal of this project
> would be to choose a few existing partitioning techniques and implement the
> corresponding graph partitioning operators for Gelly.
> Some related literature can be found [here|
> http://www.citeulike.org/user/vasiakalavri/tag/graph-partitioning].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
