You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2024/01/26 10:52:00 UTC

[jira] [Closed] (FLINK-34223) Introduce a migration tool to transfer legacy config file to new config file

     [ https://issues.apache.org/jira/browse/FLINK-34223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhu Zhu closed FLINK-34223.
---------------------------
      Assignee: Junrui Li
    Resolution: Done

master/release-1.19:
8fceb101e7e45f3fdc9357019757230bd8c16aa7

> Introduce a migration tool to transfer legacy config file to new config file
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-34223
>                 URL: https://issues.apache.org/jira/browse/FLINK-34223
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Deployment / Scripts
>            Reporter: Junrui Li
>            Assignee: Junrui Li
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.19.0
>
>
> As we transition to new configuration files that adhere to the standard YAML format, users are expected to manually migrate their existing config files. However, this process can be error-prone and time-consuming.
> To simplify the migration, we're introducing an automated script. This script leverages BashJavaUtils to efficiently convert old flink-conf.yaml files into the new config file config.yaml, thereby reducing the effort required for migration.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)