[
https://issues.apache.org/jira/browse/FLINK-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499860#comment-14499860
]
ASF GitHub Bot commented on FLINK-1670:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/581#issuecomment-93991530
What about reworking this as a library function and add it to
flink-contrib? Make this a special streaming sink and a local util that is used
in the program that receives the data.
The thing about library utils is that they are okay if they work in some
situations (as long as that is clearly indicated). They are utils after all.
Anything on the core API is expected to always work properly, making the
requirement much higher.
> 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)
