You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "shijinkui (JIRA)" <ji...@apache.org> on 2016/09/23 02:55:20 UTC

[jira] [Commented] (FLINK-4630) add netty tcp source support

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

shijinkui commented on FLINK-4630:
----------------------------------

[~StephanEwen] 
Though flink already have a SocketTextStreamFunction, netty's better performance and custom delimiter can be more helpful and flexible. SocketTextStreamFunction is read remote source like pull mode, this implements is receiver mode, that is accept the push data.
I've finish it except unit test.
What do you think of this issue? 

> add netty tcp source support
> ----------------------------
>
>                 Key: FLINK-4630
>                 URL: https://issues.apache.org/jira/browse/FLINK-4630
>             Project: Flink
>          Issue Type: New Feature
>          Components: Streaming Connectors
>            Reporter: shijinkui
>
> 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. 
> Such source service is needed in produce indeed.
> describe the source in detail below:
> 1.	source run as a netty tcp 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)