[
https://issues.apache.org/jira/browse/FLINK-34255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zakelly Lan updated FLINK-34255:
--------------------------------
Release Note:
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.
At the meantime, all the original options scattered everywhere are annotated as
@Deprecated
> FLIP-406: Reorganize State & Checkpointing & Recovery Configuration
> -------------------------------------------------------------------
>
> Key: FLINK-34255
> URL: https://issues.apache.org/jira/browse/FLINK-34255
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing, Runtime / State Backends
> Reporter: Zakelly Lan
> Assignee: Zakelly Lan
> Priority: Major
> Fix For: 2.0.0, 1.20.0
>
>
> The FLIP:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=284789560
>
> Currently, the configuration options pertaining to checkpointing, recovery,
> and state management are primarily grouped under the following prefixes:
> * *state.backend.** : configurations related to state accessing and
> checkpointing, as well as specific options for individual state backends
> * *execution.checkpointing.** : configurations associated with checkpoint
> execution and recovery
> * {*}execution.savepoint.*{*}: configurations for recovery from savepoint
> In addition, there are several individual options such as
> _{{state.checkpoint-storage}}_ and _{{state.checkpoints.dir}}_ that fall
> outside of these prefixes. The current arrangement of these options, which
> span multiple modules, is somewhat haphazard and lacks a systematic
> structure. For example, the options under the {{_CheckpointingOptions_ }}and
> {{_ExecutionCheckpointingOptions_ }}are related and have no clear boundaries
> from the user's perspective, but there is no unified prefix for them. With
> the upcoming release of Flink 2.0, we have an excellent opportunity to
> overhaul and restructure the configurations related to checkpointing,
> recovery, and state management. This FLIP proposes to reorganize these
> settings, making it more coherent by module, which would significantly lower
> the barriers for understanding and reduce the development costs moving
> forward.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
