Hi Kui.Yuan, Thanks for driving this!
In our production practice, the asynchronous I/O capability of AsyncTableFunction has shown excellent performance in batch LLM inference scenarios. We urgently need a custom timeout UDF for this use case. It would help us handle inference requests that time out—especially long-context requests—more precisely, and avoid excessive retries that could otherwise block downstream data. +1 to this proposal. Best, Xia Kui Yuan <[email protected]> 于2026年5月22日周五 11:21写道： > Hi All, > > I'd like to open a discussion for FLIP-580: AsyncTableFunction supports > user-defined timeout handling logic [1]. > > An increasing number of users are leveraging AsyncTableFunction to invoke > remote inference clusters. Such invocations are essentially remote > inference requests, which are far more prone to timeouts than regular I/O > operations. Users expect to be able to define custom handling logic when a > timeout occurs — for example, falling back to default data or accumulating > failure statistics — rather than having a TimeoutException thrown directly > and causing the entire job to fail. > > > This FLIP proposal allow users to define custom timeout handling logic > inside AsyncTableFunction. > > I've already discussed the implementation details with @Luogen offline, and > there's a POC attached [2]. > > > Looking forward to your feedback. > > Bests, > Kui.Yuan > > [1]: > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-580%3A+AsyncTableFunction+supports+user-defined+timeout+handling+logic > > [2]: > > https://github.com/yuchengxin/flink/commit/5a46cd05c48e41a582271dcb9d9842e330871a0b >
