[ 
https://issues.apache.org/jira/browse/FLINK-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349699#comment-15349699
 ] 

Josep RubiĆ³ commented on FLINK-1707:
------------------------------------

Hi Vasia,

Maybe does not make sense to continue with this implementation. Even being a 
"graph" algorithm it does not seem to fit good to distributed graph platforms. 
I know there are some implementations of the original AP and they should be 
working good (I guess you know them), maybe this is what you need for Gelly.

I also think performance should be tested but I don't have access to a real 
cluster. I've done some tests before for Hadoop with a cluster mounted in my 
laptop, but 4 nodes of 3gb of memory is the maximum I can reach. Not much 
useful :(

By the way, before doing anything I'll document an example with some iterations 
and ask some concrete doubts about the implementation.

Thanks Vasia!

> Add an Affinity Propagation Library Method
> ------------------------------------------
>
>                 Key: FLINK-1707
>                 URL: https://issues.apache.org/jira/browse/FLINK-1707
>             Project: Flink
>          Issue Type: New Feature
>          Components: Gelly
>            Reporter: Vasia Kalavri
>            Assignee: Josep RubiĆ³
>            Priority: Minor
>              Labels: requires-design-doc
>         Attachments: Binary_Affinity_Propagation_in_Flink_design_doc.pdf
>
>
> This issue proposes adding the an implementation of the Affinity Propagation 
> algorithm as a Gelly library method and a corresponding example.
> The algorithm is described in paper [1] and a description of a vertex-centric 
> implementation can be found is [2].
> [1]: http://www.psi.toronto.edu/affinitypropagation/FreyDueckScience07.pdf
> [2]: http://event.cwi.nl/grades2014/00-ching-slides.pdf
> Design doc:
> https://docs.google.com/document/d/1QULalzPqMVICi8jRVs3S0n39pell2ZVc7RNemz_SGA4/edit?usp=sharing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to