[
https://issues.apache.org/jira/browse/FLINK-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342130#comment-14342130
]
Andra Lungu commented on FLINK-1523:
------------------------------------
My first approach towards solving the second bullet point was to let the user
choose both update direction and messaging direction. However, this intoroduces
a bit of a glitch. Think that the user will choose to update the vertices based
on IN edges and to also send messages to its IN edges. This will leave OUT
edges unused and I am not sure this is the behavior we want(the same goes for
OUT-OUT edges).
Another possibility would be to add a single parameter to the
runVertexCentricIterationFunction, but then yhou would limit the possibilities
to just:
IN-OUT, OUT-IN and ALL-ALL, omitting IN-ALL, ALL-IN, OUT-ALL, OUT-IN.
Should I stick to the first approach intorduce some Javadoc warning the user
that a combination IN-IN of parameters may affect his/her programming logic?
> 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)
