[
https://issues.apache.org/jira/browse/FLINK-32384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850734#comment-17850734
]
Zhu Zhu commented on FLINK-32384:
---------------------------------
Thanks for volunteering to contribute to Flink. [~kartikeypant]
However, this is a breaking change. Therefore, we cannot do it until Flink 1.20
is released and release cycle of Flink 2.0 is started.
You are welcome to take this task if you are free at that moment.
Before that, you can take a look at other tickets.
> Remove deprecated configuration keys which violate YAML spec
> ------------------------------------------------------------
>
> Key: FLINK-32384
> URL: https://issues.apache.org/jira/browse/FLINK-32384
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Configuration
> Reporter: Zhu Zhu
> Priority: Major
> Labels: 2.0-related
> Fix For: 2.0.0
>
>
> In FLINK-29372, key that violate YAML spec are renamed to a valid form and
> the old names are deprecated.
> In Flink 2.0 we should remove these deprecated keys. This will prevent users
> (unintentionally) to create invalid YAML form flink-conf.yaml.
> Then with the work of FLINK-23620, we can remove the non-standard YAML
> parsing logic and enforce standard YAML validation in CI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
