[ 
https://issues.apache.org/jira/browse/FLINK-32740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750916#comment-17750916
 ] 

Yao Zhang commented on FLINK-32740:
-----------------------------------

Hi [~JunRuiLi],

Good question. It is also my concern.

I searched values in 
[Configuration|http://https//nightlies.apache.org/flink/flink-docs-release-1.17/zh/docs/deployment/config/]
 and there are no valid values named null(but there are some valid values named 
NONE). Some values may contain null (e.g. /dev/null) but they will not be 
translated to null. If the user intends to set the value as the string "null", 
a slight change is needed by adding double quotes (e.g. some.key: "null").

I also investigate the null literals defined in YAML standard:
 * <empty string>
 * ~
 * null (case sensitive)

Currently we may follow all the standards or only part of them, as the YAML 
parser is not used.

> 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)

Reply via email to