...

• Introduce a "config.yaml" configuration file which differs from the old configuration file named "flink-conf.yaml" as the next generation of Flink configuration files. When "config.yaml" exists in the Flink conf directory, Flink will use the standard YAML parser to parse it as the Flink configuration.

• Modify the Flink packaging process so that when generating flink-dist, the "flink-conf.yaml" file is no longer generated in the conf directory. Instead, a "config.yaml" file that conforms to the standard YAML syntax will be generated.

• For compatibility reasons, in Flink 1.x, if the old configuration file "flink-conf.yaml" exists in the Flink conf directory, Flink will ignore the new configuration file and use the old parser to parse "flink-conf.yaml" as the Flink configuration. In Flink 2.x, Flink will no longer support parsing the old configuration file flink-conf.yaml.

• To reduce the migration barrier for users and improve compatibility, we plan to extend the functionality of the standard YAML parser. The extended functionality will allow the standard YAML parser to parse List or Map type configOptions according to the FLINK-specific pattern.

Compatibility, Deprecation, and Migration Plan

...