flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasia Kalavri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1523) Vertex-centric iteration extensions
Date Mon, 02 Mar 2015 11:50:04 GMT

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

Vasia Kalavri commented on FLINK-1523:

Hi [~andralungu]! The messaging direction also determines the update direction, so there is
no need to define it twice. If a vertex sends messages to its out-going edges in superstep
i, then, it will receive messages from its in-coming edges in superstep i+1 (thus, will update
its value based on its in-coming neighbors state).

> Vertex-centric iteration extensions
> -----------------------------------
>                 Key: FLINK-1523
>                 URL: https://issues.apache.org/jira/browse/FLINK-1523
>             Project: Flink
>          Issue Type: Improvement
>          Components: Gelly
>            Reporter: Vasia Kalavri
>            Assignee: Andra Lungu
> We would like to make the following extensions to the vertex-centric iterations of Gelly:
> - allow vertices to access their in/out degrees and the total number of vertices of the
graph, inside the iteration.
> - allow choosing the neighborhood type (in/out/all) over which to run the vertex-centric
iteration. Now, the model uses the updates of the in-neighbors to calculate state and send
messages to out-neighbors. We could add a parameter with value "in/out/all" to the {{VertexUpdateFunction}}
and {{MessagingFunction}}, that would indicate the type of neighborhood.

This message was sent by Atlassian JIRA

View raw message