[
https://issues.apache.org/jira/browse/FLINK-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322183#comment-14322183
]
ASF GitHub Bot commented on FLINK-1515:
---------------------------------------
GitHub user martinkiefer opened a pull request:
https://github.com/apache/flink/pull/402
[FLINK-1515]Splitted runVertexCentricIteration into
createVertexCentricIteration and runVertexCentricIteration
I changed the process for running a vertex-centric iteration in Gelly into
a two-step procedure:
1. `createVertexCentricIteration` returns a `VertexCentricIteration` object
to allow developers to access features like broadcast data sets and
aggregators.
2. `runVertexCentricIteration` expects a `VertexCentricIteration` and
returns the `Graph`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/martinkiefer/flink iteration
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/402.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #402
----
commit 151e4c3be53bb61ee1c33b4ce4f36c03bcfabc3e
Author: Martin Kiefer <martinkie...@boxm.de>
Date: 2015-02-15T17:07:52Z
Splitted runVertexCentricIteration into createVertexIteration and
runVertexIteration to make VertexCentricIteration object accessible to
developers.
----
> [Gelly] Enable access to aggregators and broadcast sets in vertex-centric
> iteration
> -----------------------------------------------------------------------------------
>
> Key: FLINK-1515
> URL: https://issues.apache.org/jira/browse/FLINK-1515
> Project: Flink
> Issue Type: Improvement
> Components: Gelly
> Reporter: Vasia Kalavri
> Assignee: Martin Kiefer
>
> Currently, aggregators and broadcast sets cannot be accessed through Gelly's
> {{runVertexCentricIteration}} method. The functionality is already present in
> the {{VertexCentricIteration}} and we just need to expose it.
> This could be done like this: We create a method
> {{createVertexCentricIteration}}, which will return a
> {{VertexCentricIteration}} object and we change {{runVertexCentricIteration}}
> to accept this as a parameter (and return the graph after running this
> iteration).
> The user can configure the {{VertexCentricIteration}} by directly calling the
> public methods {{registerAggregator}}, {{setName}}, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
