godfreyhe opened a new pull request #13092: URL: https://github.com/apache/flink/pull/13092
## What is the purpose of the change *Many specific properties for sql client can be replace with config options from flink-conf.yaml. such as: execution.parallelism can be replaced with parallelism.default. Sql client does not support many properties from flink-conf.yaml for SET command, such as `state.backend`. As discussed in [FLINK-18161](https://issues.apache.org/jira/browse/FLINK-18161), we can deprecate sql client specific properties and support all properties from flink-conf.yaml. If there is a conflict between deprecate property and new property, just throws exception.* ## Brief change log - *Let ConfigurationEntry accept all properties, and let ExecutionEntry accept properties which are defined* - *add property conflict check when merging environment file and calling SET command* - *update environment file and document* ## Verifying this change This change added tests and can be verified as follows: - *Extended EnvironmentTest to verify the property conflict* - *Extended LocalExecutorITCase to verify SET command* ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (**yes** / no) - If yes, how is the feature documented? (not applicable / **docs** / JavaDocs / not documented) ---------------------------------------------------------------- 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]
