>
> From: Alexander Fedulov
> Sent: 01 November 2023 01:54 AM
> To: Kamal Mittal
> Cc: user@flink.apache.org
> Subject: Re: Flink custom parallel data source
>
>
>
> Flink natively supports a pull-based model for sources, where the source
operators request data from
it is feasible in this case?
From: Alexander Fedulov
Sent: 01 November 2023 01:54 AM
To: Kamal Mittal
Cc: user@flink.apache.org
Subject: Re: Flink custom parallel data source
Flink natively supports a pull-based model for sources, where the source
operators request data from the external system
; *Sent:* 31 October 2023 04:03 PM
> *To:* Kamal Mittal
> *Cc:* user@flink.apache.org
> *Subject:* Re: Flink custom parallel data source
>
>
>
> Please note that SourceFunction API is deprecated and is due to be
> removed, possibly in the next major version of Flink.
>
> Ideally
in separate threads = new
Runnable () -> serversocket.accept();
So client socket will be accepted and given to separate thread for read data
from TCP stream.
Rgds,
Kamal
From: Alexander Fedulov
Sent: 31 October 2023 04:03 PM
To: Kamal Mittal
Cc: user@flink.apache.org
Subject: Re: Flink custom paral
Please note that SourceFunction API is deprecated and is due to be removed,
possibly in the next major version of Flink.
Ideally you should not be manually spawning threads in your Flink
applications. Typically you would only perform data fetching in the sources
and do processing in the subsequent
