[
https://issues.apache.org/jira/browse/FLINK-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497855#comment-14497855
]
ASF GitHub Bot commented on FLINK-1523:
---------------------------------------
Github user andralungu commented on the pull request:
https://github.com/apache/flink/pull/537#issuecomment-93696531
Hi @vasia ,
The PR was updated to include your suggestions. Last test fails for some
reason, but that shouldn't get in the way of reviewers :)
As you can see, I went back to suqare one: I needed to test whether the
exception is thrown. I followed the degree approach. Hope it's fine!
I would like to ask you to merge this before other vertex-centric PRs
because of the following reasons:
1). FCFS
2). I had my share of merge conflicts for now :)
3). I spoke to @markus-h the other day and he said there is no rush with
#598 (which I think is a good contribution, by the way)
Thanks!
Andra
> 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)
