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:31:38 GMT

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

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

Github user StephanEwen commented on the pull request:

    https://github.com/apache/flink/pull/581#issuecomment-95528015
  
    `NetUtils.findConnectingAddress` is a useful util, when you know that the endpoint is
up already. If you can make the assumption that the master is running already you can use
that. For remote environments, this is probably a fair assumption. For local environments,
this may not matter anyways, localhost should work there.
    
    Beware of the setups where you start the cluster from one machine (that starts the master
on that machine) and launch the program from the same one. This whole network discovery is
simply a bit tricky ;-)


> 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