1996fanrui commented on code in PR #25091: URL: https://github.com/apache/flink/pull/25091#discussion_r1678676384
########## docs/content.zh/release-notes/flink-1.20.md: ########## @@ -0,0 +1,434 @@ +--- +title: "Release Notes - Flink 1.20" +--- +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +# Release notes - Flink 1.20 + +These release notes discuss important aspects, such as configuration, behavior or dependencies, +that changed between Flink 1.19 and Flink 1.20. Please read these notes carefully if you are +planning to upgrade your Flink version to 1.20. + +### Checkpoints + +#### Unified File Merging Mechanism for Checkpoints + +##### [FLINK-32070](https://issues.apache.org/jira/browse/FLINK-32070) + +The unified file merging mechanism for checkpointing is introduced to Flink 1.20 as an MVP ("minimum viable product") +feature, which allows scattered small checkpoint files to be written into larger files, reducing the +number of file creations and file deletions and alleviating the pressure of file system metadata management +raised by the file flooding problem during checkpoints. The mechanism can be enabled by setting +`state.checkpoints.file-merging.enabled` to `true`. For more advanced options and principle behind +this feature, please refer to the document of `Checkpointing`. + +#### Reorganize State & Checkpointing & Recovery Configuration + +##### [FLINK-34255](https://issues.apache.org/jira/browse/FLINK-34255) + +Currently, all the options about state and checkpointing are reorganized and categorized by +prefixes as listed below: + +1. execution.checkpointing: all configurations associated with checkpointing and savepoint. +2. execution.state-recovery: all configurations pertinent to state recovery. +3. state.*: all configurations related to the state accessing. + 1. state.backend.*: specific options for individual state backends, such as RocksDB. + 2. state.changelog: configurations for the changelog, as outlined in FLIP-158, including the options for the "Durable Short-term Log" (DSTL). + 3. state.latency-track: configurations related to the latency tracking of state access. Review Comment: ```suggestion 1. `execution.checkpointing.*`: all configurations associated with checkpointing and savepoint. 2. `execution.state-recovery.*`: all configurations pertinent to state recovery. 3. `state.*`: all configurations related to the state accessing. 1. `state.backend.*`: specific options for individual state backends, such as RocksDB. 2. `state.changelog.*`: configurations for the changelog, as outlined in FLIP-158, including the options for the "Durable Short-term Log" (DSTL). 3. `state.latency-track.*`: configurations related to the latency tracking of state access. ``` -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
