flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1670) Collect method for streaming
Date Thu, 23 Apr 2015 10:09:39 GMT

    [ https://issues.apache.org/jira/browse/FLINK-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508781#comment-14508781
] 

ASF GitHub Bot commented on FLINK-1670:
---------------------------------------

Github user ggevay commented on the pull request:

    https://github.com/apache/flink/pull/581#issuecomment-95523580
  
    OK, I see your point. I am thinking about using NetUtils.findConnectingAddress to determine
which interface is used for the communication with the cluster. For this, I would need an
IP of something in the cluster to connect to. What would be the best way to get this info?
(Maybe I could use RemoteStreamEnvironment.host, but it is a private member, so there is probably
a more standard way that I'm just overlooking.)


> 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)

Mime
View raw message