[
https://issues.apache.org/jira/browse/FLINK-15358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630787#comment-17630787
]
Weihua Hu commented on FLINK-15358:
-----------------------------------
[~chesnay] [~mxm]
As[
https://yaml.org/spec/1.2.2/#66-comments|https://yaml.org/spec/1.2.2/#66-comments]
shows, "Comments must be separated from other tokens by white space
characters".
Both current parser in flink and _escaping # via \backlash#_ are not the
standard YAML behavior.
IMO, solve this issue by migrate to standard yaml is better than introduce a
new not-compliant escaping, may be we can discuss how to resolve the scripts
problems in FLINK-23620.
> [configuration] the global configuration will trim the rest of value after a
> `#` comment sign
> ---------------------------------------------------------------------------------------------
>
> Key: FLINK-15358
> URL: https://issues.apache.org/jira/browse/FLINK-15358
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Configuration
> Affects Versions: 1.9.1
> Reporter: BlaBlabla
> Assignee: Mika Naylor
> Priority: Minor
> Labels: auto-deprioritized-major, stale-assigned
>
> Hello,
> I have to config influx metrics reporter in _conf/flink-conf.yaml_ ,however
> the password contains a # sign, then the flink will skip the rest part of the
> password after #, eg:
> *metrics.reporter.influxdb.password: xxpasssxx#blabla*
>
> *#blabla* is parsed as an end line comment.
> Can you guys fix it?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
