[
https://issues.apache.org/jira/browse/FLINK-33980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhu Zhu closed FLINK-33980.
---------------------------
Fix Version/s: 1.19.0
Resolution: Done
master/release-1.19:
06b37089f0c1cdf70ca21970a40d15c3eaba07ed
290b633c4265540d481ac563454c7f4a3e706b9d
65b8b3baad6a27e6253a93701508ba24dc8fcfe0
d02ef1cebf302c56a0d9d51664d2c7fb6f5be932
eb8af0c589ce46b091f403e848c7dc84b7e3ee8b
> Reorganize job configuration
> ----------------------------
>
> Key: FLINK-33980
> URL: https://issues.apache.org/jira/browse/FLINK-33980
> Project: Flink
> Issue Type: Technical Debt
> Components: API / Core
> Reporter: Junrui Li
> Assignee: Junrui Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> Currently, job configuration in FLINK is spread out across different
> components, including StreamExecutionEnvironment, CheckpointConfig, and
> ExecutionConfig. This distribution leads to inconsistencies among the
> configurations stored within these components. Furthermore, the methods used
> to configure these components vary; some rely on complex Java objects, while
> others use ConfigOption, which is a key-value configuration approach. This
> variation complicates the effective management of job configurations.
> Additionally, passing complex Java objects (e.g., StateBackend and
> CheckpointStorage) between the environment, StreamGraph, and JobGraph adds
> complexity to development.
> With the completion of FLIP-381, it is now time to standardize and unify job
> configuration in FLINK. The goals of this JIRA are as follows:
> # Migrate configuration from non-ConfigOption objects to use ConfigOption.
> # Adopt a single Configuration object to house all configurations.
> # Create complex Java objects, such as RestartBackoffTimeStrategyFactory,
> CheckpointStorage, and StateBackend, directly from the configuration on the
> JM side.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
