Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-03-04 Thread Jark Wu
big +1 from my side. Best, Jark On Thu, 4 Mar 2021 at 20:59, Leonard Xu wrote: > +1 for the roadmap. > > Thanks Timo for driving this. > > Best, > Leonard > > > 在 2021年3月4日,20:40,Timo Walther 写道: > > > > Last call for feedback on this topic. > > > > It seems everyone agrees to finally

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-03-04 Thread Jark Wu
big +1 from my side. Best, Jark On Thu, 4 Mar 2021 at 20:59, Leonard Xu wrote: > +1 for the roadmap. > > Thanks Timo for driving this. > > Best, > Leonard > > > 在 2021年3月4日,20:40,Timo Walther 写道: > > > > Last call for feedback on this topic. > > > > It seems everyone agrees to finally

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-03-04 Thread Leonard Xu
+1 for the roadmap. Thanks Timo for driving this. Best, Leonard > 在 2021年3月4日,20:40,Timo Walther 写道: > > Last call for feedback on this topic. > > It seems everyone agrees to finally complete FLIP-32. Since FLIP-32 has been > accepted for a very long time, I think we don't need another

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-03-04 Thread Leonard Xu
+1 for the roadmap. Thanks Timo for driving this. Best, Leonard > 在 2021年3月4日,20:40,Timo Walther 写道: > > Last call for feedback on this topic. > > It seems everyone agrees to finally complete FLIP-32. Since FLIP-32 has been > accepted for a very long time, I think we don't need another

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-03-04 Thread Timo Walther
Last call for feedback on this topic. It seems everyone agrees to finally complete FLIP-32. Since FLIP-32 has been accepted for a very long time, I think we don't need another voting thread for executing the last implementation step. Please let me know if you think differently. I will start

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-03-04 Thread Timo Walther
Last call for feedback on this topic. It seems everyone agrees to finally complete FLIP-32. Since FLIP-32 has been accepted for a very long time, I think we don't need another voting thread for executing the last implementation step. Please let me know if you think differently. I will start

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-02-26 Thread Seth Wiesman
Strong +1 Having two planners is confusing to users and the diverging semantics make it difficult to provide useful learning material. It is time to rip the bandage off. Seth On Fri, Feb 26, 2021 at 12:54 AM Kurt Young wrote: > change.> > > Hi Timo, > > First of all I want to thank you for

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-02-26 Thread Seth Wiesman
Strong +1 Having two planners is confusing to users and the diverging semantics make it difficult to provide useful learning material. It is time to rip the bandage off. Seth On Fri, Feb 26, 2021 at 12:54 AM Kurt Young wrote: > change.> > > Hi Timo, > > First of all I want to thank you for

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-02-25 Thread Kurt Young
Hi Timo, First of all I want to thank you for introducing this planner design back in 1.9, this is a great work that allows lots of blink features to be merged to Flink in a reasonably short time. It greatly accelerates the evolution speed of Table & SQL. Everything comes with a cost, as you

Re: [DISCUSS] Deprecation and removal of the legacy SQL planner

2021-02-25 Thread Kurt Young
Hi Timo, First of all I want to thank you for introducing this planner design back in 1.9, this is a great work that allows lots of blink features to be merged to Flink in a reasonably short time. It greatly accelerates the evolution speed of Table & SQL. Everything comes with a cost, as you