Hi Lu,
> 1. Is there any problem if we use Async Function for such a user case? We can
> simply drop the output and use Unordered mode.
As far as I can tell, it is similar, other than the retry strategy available
for AsyncFunctions and batching for Async Sink. Both should work on Flink.
> 2.
Thanks, Hong!
I understand that if the user case is to simply write sth to an external
service, Async Sink is a good option that provides features like batching,
state management and rate limiting. I have some follow up questions:
1. Is there any problem if we use Async Function for such a user c
Hi Lu,
Thanks for your question. See below for my understanding.
I would recommend using the Async Sink if you are writing to the external
service as the final output of your job graph, and if you don’t have the
ordered requirement that updates to the external system must be done before
update
Hi, Flink dev and users
If I want to async write to an external service, which API shall I use,
AsyncFunction or Async Sink?
My understanding after checking the code are:
1. Both APIs guarantee at least once write to external service. As both
API internally stores in-flight requests in the
