Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Ran Tao
Hi Timo, Thanks. yes. We need to make Flink's implementation of this feature more scalable and versatile. I will try to update this FLIP on the comparison and difference of the implementation of some features on other popular or commercial engines you mentioned. Let us see how to find a better

Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Timo Walther
Hi Ran, adding additional filter and selection capabilities makes sense. However, I would recommend to not only check Spark or Hive but also focus on bigger commercial players such as Snowflake, Oracle, SQL Server. In any case, maybe we should also investigate more thoughts on a Flink

Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Martijn Visser
Hi Ran, When you're creating your FLIP, please also have a look at Calcite SQL parser, since that's used by Flink [1] Best regards, Martijn [1] https://calcite.apache.org/docs/reference.html On Tue, Feb 21, 2023 at 2:10 PM Ran Tao wrote: > Yes, I totally agree with your point. The current

Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Ran Tao
Yes, I totally agree with your point. The current flink sql syntax is tiled together without classification. Let me try to summarize these four categories, not just Auxiliary Statements. And compare it with other popular engines. Thank you, Jing ! Best Regards, Ran Tao

Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Jing Ge
+ 1 for a new FLIP It would be great if we could take this opportunity to go through all current Flink SQL syntax and define a feasible classification in the FLIP. In my opinion, the 4 categories, i.e. DDL, DML, DQL, DAL , used in Spark doc [1] make sense. We will then have a better big picture

Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Ran Tao
Thanks. I will create a FLIP to illustrate some details. Best Regards, Ran Tao https://github.com/chucheng92 Jark Wu 于2023年2月21日周二 20:03写道: > Thank you, > > I think this is worth a FLIP design doc to discuss the detailed syntax. > Could you prepare a FLIP for that? > > Best, > Jark > > On

Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Jark Wu
Thank you, I think this is worth a FLIP design doc to discuss the detailed syntax. Could you prepare a FLIP for that? Best, Jark On Tue, 21 Feb 2023 at 19:37, Ran Tao wrote: > Hi, Jark. thanks. I have added a google doc. > > >

Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Ran Tao
Hi, Jark. thanks. I have added a google doc. https://docs.google.com/document/d/1hAiOfPx14VTBTOlpyxG7FA2mB1k5M31VnKYad2XpJ1I/edit?usp=sharing Jark Wu 于2023年2月21日周二 19:27写道: > Hi Ran, > > I think it’s always nice to support new syntax if it’s useful for the > users. > From my side, your syntax

Re: [DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Jark Wu
Hi Ran, I think it’s always nice to support new syntax if it’s useful for the users. From my side, your syntax table is broken. Could you share it with a Google doc or create a JIRA issue? Best, Jark > 2023年2月21日 17:51,Ran Tao 写道: > > Hi guys. When I recently used flink sql to manage

[DISCUSS] Proposal to improve Auxiliary Sql Statements

2023-02-21 Thread Ran Tao
Hi guys. When I recently used flink sql to manage internal metadata (catalog/databases/table/functions), I found that many current flink sql statements do not support filtering or some advanced syntax, however these abilities are very useful to end-users. These are some statements I have