Re: [DISCUSS] FLIP-498: AsyncTableFunction for async table function support

2025-01-27 Thread Alan Sheinberg
Hi all, The hints proposed in FLIP-313 can be added later if needed. That sounds good. Will definitely take that as a followup task to consider. So I'm +1 to continue with this FLIP, unless there are objections from > others? Since it doesn't seem that there were any objections, I'm going to

Re: [DISCUSS] FLIP-498: AsyncTableFunction for async table function support

2025-01-15 Thread Fabian Hüske
Hi all, The FLIP looks good to me and I think as well that we should continue with it. The hints proposed in FLIP-313 can be added later if needed. Thanks, Fabian On Tue, Jan 14, 2025 at 1:50 PM Timo Walther wrote: > Hi Alan, > > thanks for giving us some context. It looks like FLIP-313 has n

Re: [DISCUSS] FLIP-498: AsyncTableFunction for async table function support

2025-01-14 Thread Timo Walther
Hi Alan, thanks for giving us some context. It looks like FLIP-313 has not seen any progress for 2 years. We can still revive FLIP-313 for the hint discussion but start with config options. It makes sense that there is consistency between AsycScalarFunction and AsyncTableFunction with respect

Re: [DISCUSS] FLIP-498: AsyncTableFunction for async table function support

2025-01-13 Thread Alan Sheinberg
I just wanted to add a little bit to my response as I considered the previous FLIP. I support FLIP-313 and the proposal of the original author. I wasn't trying to take it over, but wanted to show renewed interest. I'm also focused on a smaller MVP, which is why I omitted hint support, which seeme

Re: [DISCUSS] FLIP-498: AsyncTableFunction for async table function support

2025-01-13 Thread Alan Sheinberg
Thanks for the responses Timo, Dawid. > However, why have you decided to resubmit the FLIP with a newer number > rather than following up on FLIP-313? The only difference I see between the > two FLIPs is the options/hints design. Could you elaborate where the > differences come from? I think yo

Re: [DISCUSS] FLIP-498: AsyncTableFunction for async table function support

2025-01-13 Thread Dawid Wysakowicz
Generally what is suggested here makes sense to me. However, why have you decided to resubmit the FLIP with a newer number rather than following up on FLIP-313? The only difference I see between the two FLIPs is the options/hints design. Could you elaborate where the differences come from? Best,

Re: [DISCUSS] FLIP-498: AsyncTableFunction for async table function support

2025-01-13 Thread Timo Walther
Hi Alan, thanks for proposing this FLIP. I agree that AsyncTableFunction is very similar to AsyncScalarFunction and luckily, the Python component has laid the foundation for this proposal. Nothing to add from my side. +1 for voting. Regards, Timo On 02.01.25 20:47, Alan Sheinberg wrote: I

[DISCUSS] FLIP-498: AsyncTableFunction for async table function support

2025-01-02 Thread Alan Sheinberg
I'd like to start a discussion of FLIP-498: AsyncTableFunction for async table function support [1] This feature proposes exposing AsyncTableFunction as a proper user defined function. The type already exists for Lookup Joins, but isn't usable as other UDFs. This FLIP would bring it up to parity