[
https://issues.apache.org/jira/browse/FLINK-32740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750667#comment-17750667
]
Junrui Li commented on FLINK-32740:
-----------------------------------
[~paul8263]
Could you provide more details about the problem you are trying to solve?
IIUC, after using the standard yaml parser, it naturally supports reading empty
value or null value, and parses the value into null. Then the value will not be
put into the Configuration object. It can achieve the effect of using the
default value of the configuration item.
> Introduce literal null value for flink-conf.yaml
> ------------------------------------------------
>
> Key: FLINK-32740
> URL: https://issues.apache.org/jira/browse/FLINK-32740
> Project: Flink
> Issue Type: Improvement
> Components: API / Core
> Affects Versions: 1.15.4
> Reporter: Yao Zhang
> Priority: Minor
>
> Hi community,
> Currently in flink-conf.yaml we only consider simplified YAML syntax like key
> value pairs. And it might not be the right timing to indroduce YAML parser.
> As [FLINK-23620 |https://issues.apache.org/jira/browse/FLINK-23620] has been
> stated, there might be some keys that violate the YAML naming conventions.
> The current situation is, if we want to unset the value (or set the value as
> its default), what we could do is to remove the key value pair completely or
> leave the value blank (e.g. `rest.port: `). It might be inconvenient or less
> readable for conf file that controlled by other applications.
> So is it necessary to add some special literal values that will be translated
> to the real null value? For YAML we usually see ~, null or empty value as
> null value. If necessary I would like to do this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
