[
https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445140#comment-17445140
]
Chesnay Schepler commented on FLINK-23620:
------------------------------------------
The bash startup scripts (e.g., bin/config.sh) also read from the configuration
and rely on the config being simple key-value pairs. We'd ether have to forbid
nested structures for certain keys, beef up the parsing in the scripts or defer
the parsing to the BashJavaUtils.
The bash E2E test scripts make the same assumption.
If certain keys can't work with nested structures, and we can't replace those
due to backwards-compatibility concerns, then that is fine as far as I'm
concerned.
> Introduce proper YAML parsing to Flink's configuration
> ------------------------------------------------------
>
> Key: FLINK-23620
> URL: https://issues.apache.org/jira/browse/FLINK-23620
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Mika Naylor
> Assignee: Mika Naylor
> Priority: Minor
> Labels: pull-request-available
>
> At the moment, the YAML parsing for Flink's configuration file
> ({{conf/flink-conf.yaml)}} is pretty basic. It only supports basic key value
> pairs, such as:
> {code:java}
> a.b.c: a value
> a.b.d: another value{code}
> As well as supporting some invalid YAML syntax, such as:
> {code:java}
> a: b: value{code}
>
> Introducing proper YAML parsing to the configuration component would let
> Flink users use features such as nested keys, such as:
> {code:java}
> a:
> b:
> c: a value
> d: another value{code}
> as well as make it easier to integrate configuration tools/languages that
> compile to YAML, such as Dhall.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
