[
https://issues.apache.org/jira/browse/FLINK-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382664#comment-14382664
]
ASF GitHub Bot commented on FLINK-1523:
---------------------------------------
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/537#discussion_r27255825
--- Diff:
flink-staging/flink-gelly/src/main/java/org/apache/flink/graph/Graph.java ---
@@ -1118,17 +1118,61 @@ public boolean filter(Edge<K, EV> edge) {
}
/**
- * Create a Vertex-Centric iteration on the graph.
- *
+ * Create a Vertex-Centric iteration on the graph. inDegrees, outDegrees
+ * and the total number of vertices are set here in order to be
retrieved
+ * later on within the iteration.
+ *
+ * Also, The user can define the direction in which the updates are
performed
+ * and in which the messages are sent. The function below tackles the
regular
+ * use-case where updates of the in-neighbors are used to calculate
state
+ * and messages are sent to out-neighbors.
+ *
* @param vertexUpdateFunction the vertex update function
* @param messagingFunction the messaging function
* @param maximumNumberOfIterations maximum number of iterations to
perform
* @return
*/
- public <M> VertexCentricIteration<K, VV, M, EV>
createVertexCentricIteration(
+ public <M, NV extends Serializable> VertexCentricIteration<K, VV, M,
EV> createVertexCentricIteration(
--- End diff --
NV is never used?
> 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
(v6.3.4#6332)
