[
https://issues.apache.org/jira/browse/FLINK-34377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821257#comment-17821257
]
xingbe commented on FLINK-34377:
--------------------------------
Hi [~zhuzh] [~lincoln.86xy] , I've completed the testing work as described and
all test results align with expectations. The verification process was as
follows:
For Test 1, I created a new Flink SQL job on a yarn-session cluster and
configured it using the config.yaml file, specifically setting the
parallelism.default. The job ran with the expected level of parallelism.
For Test 2, I utilized the migration script 'bin/migrate-config-file.sh' to
transition an existing job's flink-conf.yaml to the new config.yaml format. The
script successfully converted the configuration as anticipated, and the job ran
with the proper settings per the new configuration.
So I think it looks good and works as desired.
> 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)
