GitHub user shijinkui opened a pull request:

    https://github.com/apache/bahir-flink/pull/7

    [BAHIR-72] support netty: pushed tcp/http connector

    When source stream get start, listen a provided tcp port, receive stream 
data from user data source.
    This netty tcp source is keepping alive and end-to-end, that is from 
business system to flink worker directly.
    1.  source run as a netty tcp and http server
    2.  user provide a tcp port, if the port is in used, increace the port 
number between 1024 to 65535. Source can parallel.
    3.  callback the provided url to report the real port to listen
    4.  user push streaming data to netty server, then collect the data to flink

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

    $ git pull https://github.com/shijinkui/bahir-flink netty_connector

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

    https://github.com/apache/bahir-flink/pull/7.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 #7
    
----
commit a189597d11bfabb8af2fc671dd68cf8cc57d3fb2
Author: shijinkui <[email protected]>
Date:   2016-10-24T11:40:24Z

    [BAHIR-72] support netty: pushed tcp/http connector
    When source stream get start, listen a provided tcp port, receive stream 
data from user data source.
    This netty tcp source is keepping alive and end-to-end, that is from 
business system to flink worker directly.
    1.  source run as a netty tcp and http server
    2.  user provide a tcp port, if the port is in used, increace the port 
number between 1024 to 65535. Source can parallel.
    3.  callback the provided url to report the real port to listen
    4.  user push streaming data to netty server, then collect the data to flink

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to