Yes Gordon, it's obviously gave me a starting point to think about.
On Wed, Feb 3, 2021, 12:02 PM Tzu-Li (Gordon) Tai
wrote:
> Hi,
>
> There is no out-of-box Flink source/sink connector for this, but it isn't
> unheard of that users have implemented something to support what you
> outlined.
>
>
Hi Raghavendar,
Yes , you are right. Your approach is correct ,and it is the most
straightforward one.but I was just thinking about the possibilities of my
question mentioned.
Thanks
EK
On Wed, Feb 3, 2021, 12:02 PM Raghavendar T S
wrote:
> Hi Ejaskhan
>
> As per my understanding, this
Hi,
There is no out-of-box Flink source/sink connector for this, but it isn't
unheard of that users have implemented something to support what you
outlined.
One way to possibly achieve this is: in terms of a Flink streaming job
graph, what you would need to do is co-locate the source (which
Hi Ejaskhan
As per my understanding, this approach will require your data source to run
a HTTP server within itself (embedded web server) and I am not sure If it
is a good design. It looks like you are trying to build a
synchronous(client-server model) processing model in Flink. But Flink is
Team,
It's just a random thought.
Can I make the Flink application exposing a rest endpoint for the data
source? So a client could send data to this endpoint. Subsequently, Flink
processed this data and responded to the client application through the
endpoint, like a client-server model.
Thanks
