[
https://issues.apache.org/jira/browse/FLINK-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543408#comment-14543408
]
ASF GitHub Bot commented on FLINK-1523:
---------------------------------------
Github user andralungu commented on the pull request:
https://github.com/apache/flink/pull/537#issuecomment-101978637
Hi @vasia,
I had a look at the new branch. The changes look good, degrees are no
longer exposed to the user and the current approach removes the need to
subclass Vertex. :+1:
The only small remark/comment I have comes from a user perspective:
- let's say that, by mistake, I forgot to set the degrees option;
- let's also say I was too "busy" to read the manual :)
- result: I will get -1 instead of the expected number of degrees per vertex
I understand why you had to pass -1 there; it should be of the same type as
the degrees. However, maybe we can come up with some way to hint users that
they should not forget to set the corresponding options. Adding an extra line
in the documentation might not suffice.
> 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)
