Zakelly opened a new pull request #16153: URL: https://github.com/apache/flink/pull/16153
## What is the purpose of the change This change provides configurations as well as APIs to configure ChangelogStateBackend. Base on the discussion before (https://lists.apache.org/thread.html/ra178ce29088b1da362d98a5a6d8c7be48051caf1637ee24261738217%40%3Cdev.flink.apache.org%3E) and the design doc (https://docs.google.com/document/d/13AaCf5fczYTDHZ4G1mgYL685FqbnoEhgo0cdwuJlZmw/edit?usp=sharing, see Option 3), we make a refined version of loading ChangelogStateBackend. Please check the brief change log below. ## Brief change log - Define consistent override and combination policy (flag + state backend) in different config levels. - Differentiate explicitly the meaning of "enable flag" = true/false/unset. - Hide ChangelogStateBackend from users. ## Verifying this change This change added some test cases in ```ChangelogStateBackendLoadingTest```. Including tests for configuration overriding and stream graph validation. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): yes, tests in ```flink-statebackend-changelog``` now depends on ```flink-streaming-java_2.11```. - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: yes, add ```enableChangelogStateBackend``` and ```isChangelogStateBackendEnabled``` in ```StreamExecutionEnvironment``` - The serializers: no - The runtime per-record code paths (performance sensitive): no, but ChangelogStateBackend itself may affect the per-record code paths. - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: yes - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? yes. - If yes, how is the feature documented? Docs and JavaDocs. -- 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]
