@Timo Walther @Yanquan Lv @Jim Hughes
Thank you for saying that the FLIP looks good.
@Feng Jin, +1 to what Timo already said above, does that address your
concern?
This FLIP seems to pretty uncontroversial so far so perhaps we can start a
vote soon? Maybe tomorrow before the 4th of July
Hi Natea,
the FLIPs looks good to me. Looking for forward to it.
@Feng: TypeInferenceUtil#generateSignature considers parameter names if
they have been specified. We can further evolve this function (e.g.
improving the result type information), but this is not part of the
FLIP. This requires
Hi, Natea,
Thank you for initiating this FLIP.
Have you considered displaying parameter names? This would make it easier
for users to use named parameters.
Best,
Feng
On Sun, Jun 30, 2024 at 3:49 PM Yanquan Lv wrote:
> Hi, Natea. This FLIP looks good from my side.
> I also look forward to
Hi, Natea. This FLIP looks good from my side.
I also look forward to showing the return type, as well as auxiliary
information such as comments or usage, although the current implementation
does not include this part.
Natea Eshetu Beshada 于2024年6月26日周三 03:01写道：
> Oh no haha, yes thanks for
Oh no haha, yes thanks for pointing that out Jim! Of course I make a typo
on an editable format like email :)
On Tue, Jun 25, 2024 at 11:20 AM Jim Hughes
wrote:
> Hi Natea,
>
> Looks good. As a note, in the title of this email, a number got switched!
> FLIP-456 is about compiled plans for
Hi Natea,
Looks good. As a note, in the title of this email, a number got switched!
FLIP-456 is about compiled plans for batch operators. :)
The link below is correct.
Cheers,
Jim
On Tue, Jun 25, 2024 at 1:29 PM Natea Eshetu Beshada
wrote:
> Hello all,
>
> I would like to kickstart the
Hello all,
I would like to kickstart the discussion of FLIP-465: Introduce DESCRIBE
FUNCTION [1].
The proposal is to add SQL syntax that would allow users to describe the
metadata of a given function.
I look forward to hearing feedback from the community.
[1]
