twalthr commented on issue #9203: [FLINK-13375][table-api] Move ExecutionConfigOptions and OptimizerConfigOptions to table-api URL: https://github.com/apache/flink/pull/9203#issuecomment-514116845 In my opinion we should distinguish between the SQL language and the table ecosystem. 1. In most presentations, documentation, and in discussions we refer to the "table ecosystem" or "Table API" than "SQL API". 2. This is also represented in the Maven module names. `flink-sql-client` and `flink-sql-parser` are around SQL. `flink-table-XXX` are broader and cover working with the concept of "tables" and relational algebra (independent of SQL). 3. The Table API will receive a lot of new features such as machine learning via `flatMap, flatAggregate` etc. in the future. This has nothing to do with SQL and would confuse if runtime options are named like this. Any other opinions @dawidwys @aljoscha?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
