[ https://issues.apache.org/jira/browse/FLINK-15358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630427#comment-17630427 ]
Chesnay Schepler commented on FLINK-15358: ------------------------------------------ It's not "easy" at all. Various scripts in Flink rely on the file containing key-value pairs for parsing/modifications. See FLINK-23620. ??We could at least support escaping # via \backlash# even without moving to a full-blown parser.?? Is that YAML-compliant? Let's not introduce another problem we have to fix down the line. > [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)