[
https://issues.apache.org/jira/browse/FLINK-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14540037#comment-14540037
]
ASF GitHub Bot commented on FLINK-1885:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/598#issuecomment-101321028
I had a look at this, and it actually looks quite good. The basic idea
seems to be that you emit the original vertex if no update happens.
It would be nice to not have the `isLastCollected` flag in the user-facing
classes. If you could have a dedicated vertex-centric bulk coGroup, with its
own output collector, you can track this in the OutputCollector. I think that
would be cleanrer with respect to the user-facing API.
Otherwise, I think this is a good addition...
> Bulk mode for gelly
> -------------------
>
> Key: FLINK-1885
> URL: https://issues.apache.org/jira/browse/FLINK-1885
> Project: Flink
> Issue Type: Improvement
> Components: Gelly
> Reporter: Markus Holzemer
> Assignee: Markus Holzemer
> Priority: Minor
>
> For my research I need to execute graph algorithm with delta iterations and
> with bulk iterations. So I added an execution mode to gelly that executes the
> vertex centric iteration with a bulk iteration.
> Since gelly normally keeps the whole graph in the solution set of the delta
> iteration, it can only handle graphs that fit into the distributed memory of
> ones nodes (correct me if I am wrong). So a bulk mode could also be usefull
> for handling graphs that do not fit in memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
