[
https://issues.apache.org/jira/browse/FLINK-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486461#comment-14486461
]
ASF GitHub Bot commented on FLINK-1670:
---------------------------------------
Github user mbalassi commented on the pull request:
https://github.com/apache/flink/pull/581#issuecomment-91082306
Thanks for picking up the issue, @ggevay. I would like to add to the list
Stephan mentioned:
I personally prefer the name collect for the method, it can still return a
iterator, but it is nice to keep the batch and streaming APIs in sync and we
already have a batch collect method. It is safer so people do not potentially
confuse it with the `IterativeDataStream`.
> Collect method for streaming
> ----------------------------
>
> Key: FLINK-1670
> URL: https://issues.apache.org/jira/browse/FLINK-1670
> Project: Flink
> Issue Type: New Feature
> Components: Streaming
> Affects Versions: 0.9
> Reporter: Márton Balassi
> Assignee: Gabor Gevay
> Priority: Minor
>
> A convenience method for streaming back the results of a job to the client.
> As the client itself is a bottleneck anyway an easy solution would be to
> provide a socket sink with degree of parallelism 1, from which a client
> utility can read.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
