+1 (non-binding)

Thanks for driving this - the convention-based timeout() mirroring eval
keeps it consistent and backward-compatible.


Best,
Weiqing

On Sun, Jun 7, 2026 at 7:03 PM Xuyang <[email protected]> wrote:

> +1(binding)
>
>
> --
>
>     Best!
>     Xuyang
>
>
>
> 在 2026-06-05 12:56:48,"Yuepeng Pan" <[email protected]> 写道:
> >Thanks for driving it!
> >
> >+1(non-binding)
> >
> >Best,
> >Yuepeng Pan
> >
> >Gen Luo <[email protected]> 于2026年6月5日周五 11:38写道:
> >
> >> Thanks for driving this!
> >>
> >> +1(non-binding)
> >>
> >> Best,
> >> Gen
> >>
> >> On Fri, Jun 5, 2026 at 9:10 AM Lincoln Lee <[email protected]>
> wrote:
> >>
> >> > +1(binding)
> >> >
> >> >
> >> > Best,
> >> > Lincoln Lee
> >> >
> >> >
> >> > Kui Yuan <[email protected]> 于2026年6月4日周四 10:55写道:
> >> >
> >> > > Hi everyone,
> >> > >
> >> > > I would like to start a vote on FLIP-580: AsyncTableFunction
> supports
> >> > > user-defined timeout handling logic.
> >> > >
> >> > > The FLIP proposal allow users to define custom timeout handling
> logic
> >> > > inside AsyncTableFunction. 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.
> >> > >
> >> > > FLIP:
> >> > >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-580%3A+AsyncTableFunction+supports+user-defined+timeout+handling+logic
> >> > >
> >> > > Discussion thread:
> >> > > https://lists.apache.org/thread/nv5vvmqwgzjq14fzwb63nos5t3xgq4fz
> >> > >
> >> > > The vote will be open for at least 72 hours unless there is an
> >> > > objection or insufficient votes.
> >> > >
> >> > > Thanks,
> >> > > Kui.Yuan
> >> > >
> >> >
> >>
>

Reply via email to