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

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_r28643293
  
    --- Diff: docs/gelly_guide.md ---
    @@ -380,6 +380,16 @@ all aggregates globally once per superstep and makes 
them available in the next
     
     * <strong>Broadcast Variables</strong>: DataSets can be added as 
[Broadcast Variables](programming_guide.html#broadcast-variables) to the 
`VertexUpdateFunction` and `MessagingFunction`, using the 
`addBroadcastSetForUpdateFunction()` and 
`addBroadcastSetForMessagingFunction()` methods, respectively.
     
    +* <strong>Number of Vertices</strong>: Accessing the total number of 
vertices within the iteration. This property can be set using the 
`setOptNumVertices()` method.
    +
    +The number of vertices can then be accessed in the vertex update function 
and in the messaging function using the `getNumberOfVertices()` method.
    +
    +* <strong>Degrees</strong>: Accessing the in/out degree for a vertex 
within an iteration. This property can be set using the `setOptDegrees()` 
method.
    +
    --- End diff --
    
    same


> 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)

Reply via email to