wuchong commented on issue #9203: [FLINK-13375][table-api] Move ExecutionConfigOptions and OptimizerConfigOptions to table-api URL: https://github.com/apache/flink/pull/9203#issuecomment-514100857 Hi @twalthr , I agree with the hierarchical naming. Regarding to why choosing the `sql.` prefix, there are 3 reasons: 1. The `sql.` prefix is more widely used in Hadoop ecosystem, for example, `spark.sql.xxx` instead of `spark.dataframe.xxx`. We also want to promote SQL as the first citizen in Table API / SQL. 2. The `table.` prefix may confuse users what "table" does it mean? The table module or `Table` in Table API or table in database? 3. We have some options contains `table` in the key, for example: `sql.resource.hash-agg.table.memory.mb`, `sql.optimizer.reuse.table-source.enabled`. If we use `table.` prefix, it may conflict with the "table" in the option name. What do you think? @twalthr @godfreyhe
---------------------------------------------------------------- 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
