flink-planner, precision things maybe cannot be
supported.
Best,
Jingsong Lee
On Tue, Oct 8, 2019 at 5:58 PM zha...@lenovocloud.com <
zha...@lenovocloud.com> wrote:
unsubscribe
zha...@lenovocloud.com
From: Jark Wu
Date: 2019-10-08 17:29
To: dev
Subject: Re: [DISCUSS] FLIP-65: Ne
> > zha...@lenovocloud.com> wrote:
> >
> >> unsubscribe
> >>
> >>
> >>
> >> zha...@lenovocloud.com
> >>
> >> From: Jark Wu
> >> Date: 2019-10-08 17:29
> >> To: dev
> >> Subject: Re: [
ud.com
From: Jark Wu
Date: 2019-10-08 17:29
To: dev
Subject: Re: [DISCUSS] FLIP-65: New type inference for Table API UDFs
Hi Timo,
Thanks for the proposal, a big +1 to the FLIP, especially this enables the
unified `TableEnvironment.registerFunction()`.
I think the design documentation is prett
subscribe
>
>
>
> zha...@lenovocloud.com
>
> From: Jark Wu
> Date: 2019-10-08 17:29
> To: dev
> Subject: Re: [DISCUSS] FLIP-65: New type inference for Table API UDFs
> Hi Timo,
>
> Thanks for the proposal, a big +1 to the FLIP, especially this enables the
> unif
unsubscribe
zha...@lenovocloud.com
From: Jark Wu
Date: 2019-10-08 17:29
To: dev
Subject: Re: [DISCUSS] FLIP-65: New type inference for Table API UDFs
Hi Timo,
Thanks for the proposal, a big +1 to the FLIP, especially this enables the
unified `TableEnvironment.registerFunction()`.
I think
Hi Timo,
Thanks for the proposal, a big +1 to the FLIP, especially this enables the
unified `TableEnvironment.registerFunction()`.
I think the design documentation is pretty good enough, I only left some
minor comments there.
Best,
Jark
On Fri, 4 Oct 2019 at 23:54, Timo Walther wrote:
> Hi
Hi everyone,
I would like to propose FLIP-65 that describes how we want to deal with
data types and their inference/extraction in the Table API in the
future. I have collected many comments, shortcomings, issues from users
and trainings in last years that went into the design. It completes
