[
https://issues.apache.org/jira/browse/FLINK-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529347#comment-14529347
]
ASF GitHub Bot commented on FLINK-1523:
---------------------------------------
Github user andralungu commented on the pull request:
https://github.com/apache/flink/pull/537#issuecomment-99232613
Hey @vasia ,
Everyone is acting as though I do not want to make these methods
user-freindly. I do :), it's just not possible.
Keep in mind that in the VertexUpdateFunction and in the MessagingFunction
you can only access the vertex in the updateVertex() and sendMessages()
methods.
getDirection(), getBroadcastSet() return a single value for all the
vertices. getDegree() returns one value for each of the vertices. As
previously implied, you cannot access the vertex in these classes. The only
very ugly solution is to give it the entire DataSet and to constantly filter
it. You basically have the degree of the vertex in the Tuple3, but this
information is hidden from the user.
> 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)
