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 approac
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 expos
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
meant
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
Thanks Till and Sendoh
On 5 January 2018 at 12:38, Till Rohrmann wrote:
> Hi Alberto,
>
> currently, the queryable state is not exposed via a REST interface. You
> have to use the QueryableStateClient for that [1]. If it's not possible to
> directly connect to the machines running your Flink clu
Hi Alberto,
currently, the queryable state is not exposed via a REST interface. You
have to use the QueryableStateClient for that [1]. If it's not possible to
directly connect to the machines running your Flink cluster, then you can
also expose the values via the metric system as Sendoh proposed.
I think the first requirement is possible by using accumulator or metric, or?
Cheers,
Sendoh
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
* Read from Rest API in streaming / micro batch some values ( Example: read
last Value of BitCoin)
* Expose Queriable State as as queriable Rest API (Example: Expose
intermediate results on demmand)
