[ https://issues.apache.org/jira/browse/FLINK-23620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mika Naylor updated FLINK-23620: -------------------------------- Description: 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. was: 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. > 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 > Priority: Minor > > 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.3.4#803005)