[
https://issues.apache.org/jira/browse/FLINK-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505588#comment-14505588
]
ASF GitHub Bot commented on FLINK-1523:
---------------------------------------
Github user andralungu commented on the pull request:
https://github.com/apache/flink/pull/537#issuecomment-94915061
Hi @vasia ,
I added some answers to your inline comments! I will push my latest version
for this tomorrow.
Regarding the suggestion that the Vertex class might not be the best place
for the getDegree methods, there is a reason why implementing this took a while
^^. I wanted to make the degrees available only in the iteration. The problem
is that with the current code(this one and the one in "production"), a vertex
is only accessible in the updateVertex() method. This means that there is no
way to get the vertex within the iteration, you don't have a Vertex object,
it's not something you send to the class. That was the quick workaround I found
for this issue. If you know a better way, I am eager to hear your suggestions.
Thanks! :)
> 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)
