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 Tue, 21 Apr 2015 19:19:58 GMT

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

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

Github user StephanEwen commented on the pull request:

    https://github.com/apache/flink/pull/581#issuecomment-94911176
  
    This looks much better. Being not densely integrated into the DataStream makes it easier
to maintain.
    
    The `InetAddress.getLocalHost().getHostAddress()` problem still persist in my opinion.
This command gives some host name, usually the one tied to the local device.
    
    Many machines (especially cloud servers) have various addresses and various hostnames,
not all of them exposed. Take an EC2 instance, which has at least three network interfaces
      - loopback: hostname is "localhost" or whatever you configure as the hostname (it is
"herman" in my case). Not necessarily registered at the DNS.
      - A cloud internal one "10.x.x.x", hostname is something like "ec2-europ1-z3-81-internal.amazonaws.com"

      - An external one, such as "203.0.113.25", hostname is something like "ec2-203-0-113-25.compute-1.amazonaws.com"

    
    If your command returns "herman", this is probably not of much help, when what you want
is actually "ec2-europ1-z3-81-internal.amazonaws.com"



> 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