GitHub user medcv opened a pull request:

    https://github.com/apache/flink/pull/5996

    [FLINK-9343] [Example] Add Async Example with External Rest API call

    ## What is the purpose of the change
    
    *(For example: This pull request makes task deployment go through the blob 
server, rather than through RPC. That way we avoid re-transferring them on each 
deployment (during recovery).)*
    
    
    ## Brief change log
    
    - Async I/O is a good way to call External resources such as REST API and 
enrich the stream with external data.
    
    - Adding example to simulate Async GET api call on an input stream.
    
    
    ## Verifying this change
    
    This change is a trivial rework / code cleanup without any test coverage.
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): (no)
      - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
      - The serializers: (no)
      - The runtime per-record code paths (performance sensitive): (no)
      - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
      - The S3 file system connector: (no)
    
    ## Documentation
    
      - Does this pull request introduce a new feature? (no)
      - If yes, how is the feature documented? (not applicable / docs / 
JavaDocs / not documented)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/medcv/flink patch-3

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5996.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5996
    
----
commit 2d6bfa1662b6c514cbfb211ccdaef369c4594622
Author: Yazdan.JS <y_shirvany@...>
Date:   2018-05-12T05:41:07Z

    [FLINK-9343] Add Async Example with External Rest API call

----


---

Reply via email to