Hi all, I'd like to start a discussion for the new features lacking support of Sql-client.
I've seen the new DDL syntax that SQL client lacks support for many times. For every new DDL syntax, we need to add support in sql-client. Add a corresponding SqlCommand in sql-client, otherwise this DDL is still not working in sql-client. But it looks like developers always forgot to add support in sql-client. Lots of DDL features just be added in parser and planner, but lack sql-client support, so users will wait for the next release. Just like: https://issues.apache.org/jira/browse/FLINK-7151 https://issues.apache.org/jira/browse/FLINK-17198 https://issues.apache.org/jira/browse/FLINK-15468 https://issues.apache.org/jira/browse/FLINK-15175 How to solve this? I think we have two options: 1. Unify the parser in sql-client and TableEnvironment truly. Really make sql-client have all abilities from TableEnvironment. sql-client just forward sql to TableEnvironment. Can it be? 2. A new testing framework mechanism: We can make sql-related tests more "up front", we can move e2e tests (I think we are doing now) and it cases to sql-client oriented. This may require a new testing framework mechanism, for example, we can do something like hive sql testing [1] to sql-client oriented. In this way, the testing can cover more horizontal and vertical and it is easy to migrate tests from other systems too. And I think, Flink's DDLs are enough stronger to support pure SQLs testing. What do you think? [1]https://github.com/apache/hive/tree/master/ql/src/test/queries Best, Jingsong
