flink
flink copied to clipboard
apache
[FLINK-33576][core] Introduce new Flink conf file 'config.yaml' supporting standard YAML syntax.
What is the purpose of the change
Introduce new Flink conf file 'config.yaml' supporting standard YAML syntax.
Brief change log
- Introduce new Flink conf file 'config.yaml' supporting standard YAML syntax.
- Change the UT case to use new conf file.
Verifying this change
This change is already covered by existing tests.
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, 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)
CI report:
- 7f422b491adbee56d9dfa3f346167cbdfdc88ada Azure: SUCCESS
Bot commands
The @flinkbot bot supports the following commands:-
@flinkbot run azurere-run the last Azure build
Hi @zhuzhurk , Thanks for reviewing. I've updated the PR with the necessary changes. Please take a look~
Here are some clarifications I'd like to make:
-
Concerning the thread safety issues of the GlobalConfiguration.isStandardYaml state during concurrent tests, the current testing framework in Flink ensures tests are run sequentially between different test classes within the same process. This setup means we only need to ensure the consistency of that state upon the completion of each test class.
-
Regarding the updates needed for comments within the code and specific code references to "flink-conf.yaml" (for example, in YarnTestBase), I intend to address these adjustments in a follow-up task. This subsequent task will involve updating the default configuration file in flink-dist to config.yaml, at which time I plan to collectively revise both the comments in the code and the relevant code references.