You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lincoln lee (Jira)" <ji...@apache.org> on 2024/02/27 14:26:00 UTC
[jira] [Closed] (FLINK-34377) Release Testing: Verify FLINK-33297 Support standard YAML for FLINK configuration
[ https://issues.apache.org/jira/browse/FLINK-34377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lincoln lee closed FLINK-34377.
-------------------------------
Resolution: Fixed
[~xiasun]Thanks for your testing!
> Release Testing: Verify FLINK-33297 Support standard YAML for FLINK configuration
> ---------------------------------------------------------------------------------
>
> Key: FLINK-34377
> URL: https://issues.apache.org/jira/browse/FLINK-34377
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Configuration
> Affects Versions: 1.19.0
> Reporter: Junrui Li
> Assignee: xingbe
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.19.0
>
>
> This issue aims to verify FLIP-366.
> Starting with version 1.19, Flink has officially introduced full support for the standard YAML 1.2 syntax. For detailed information, please refer to the Flink website:https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#flink-configuration-file
> We may need to cover the following two types of test cases:
> Test 1: For newly created jobs, utilize a config.yaml file to set up the Flink cluster. We need to verify that the job runs as expected with this new configuration.
> Test 2: For existing jobs, migrate the legacy flink-conf.yaml to the new config.yaml. Test the job runs just like before post-migration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)