Hi devs, I'd like to start a discussion on FLIP-425: Asynchronous Execution Model[1], which is a sub-FLIP of FLIP-423: Disaggregated State Storage and Management[2].
FLIP-425 introduces a non-blocking execution model leveraging the asynchronous APIs introduced in FLIP-424[3]. For the whole story please read the FLIP-423[2], and this thread is aimed to discuss the details of "FLIP-425: Asynchronous Execution Model". Regarding the details of this FLIP, there have been some discussions here[4], mainly focusing on framework overhead profiling, watermark processing, etc. Please see link[4] for the context. Looking forward to hearing from you! [1] https://cwiki.apache.org/confluence/x/S4p3EQ [2] https://cwiki.apache.org/confluence/x/R4p3EQ [3] https://cwiki.apache.org/confluence/x/SYp3EQ [4] https://lists.apache.org/thread/ct8smn6g9y0b8730z7rp9zfpnwmj8vf0 Best, Yanfei
