[
https://issues.apache.org/jira/browse/FLINK-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486464#comment-14486464
]
ASF GitHub Bot commented on FLINK-1670:
---------------------------------------
Github user mbalassi commented on a diff in the pull request:
https://github.com/apache/flink/pull/581#discussion_r28028612
--- Diff:
flink-staging/flink-streaming/flink-streaming-core/src/main/java/org/apache/flink/streaming/api/datastream/DataStream.java
---
@@ -1165,6 +1168,7 @@ protected ExecutionConfig getExecutionConfig() {
public DataStreamSink<OUT> writeToSocket(String hostName, int port,
SerializationSchema<OUT, byte[]> schema) {
DataStreamSink<OUT> returnStream = addSink(new
SocketClientSink<OUT>(hostName, port, schema));
+ returnStream.setParallelism(1);
return returnStream;
--- End diff --
A comment here clarifying the reasons for this would be nice. :)
> 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)
