[
https://issues.apache.org/jira/browse/FLINK-35642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856140#comment-17856140
]
Junrui Li commented on FLINK-35642:
-----------------------------------
[~blackpighe] Could you try to use the new config file 'config.yaml'? This was
introduced in Flink 1.19 and supports the standard YAML syntax. The issue you
meet is the limitation of legacy configuration parser. And it is deprecated and
is planned to be removed in Flink 2.0. For more detailed information, you may
refer to the Flink documentation regarding the configuration file at:
[https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#flink-configuration-file]
> parsing the configuration file in flink, when configuring the s3 key, if
> there is contain # char, the correct key will be split
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-35642
> URL: https://issues.apache.org/jira/browse/FLINK-35642
> Project: Flink
> Issue Type: Bug
> Components: API / Core
> Affects Versions: 1.14.3, 1.19.0, 1.20.0, 1.19.1
> Reporter: blackpighe
> Priority: Major
> Fix For: 1.19.1
>
> Attachments: image-2024-06-19-11-45-05-871.png
>
>
> parsing the configuration file in flink, when configuring the s3 key, if
> there is contain # char, the correct key will be split。
>
> such as:
>
> s3.secret-key: Minio#dct@78
>
>
> !image-2024-06-19-11-45-05-871.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
