Page History

...

• Compatibility:

  There is no compatibility issue here because we use different configuration file names to ensure compatibility. The default configuration file will be changed to "flink-config.yaml" and parsed by the standard YAML parser. If users prefer to use the old parser, they can create a "flink-conf.yaml" file in the conf directory.

  Note that there are some behavior changes when using the standard YAML parser as follows:

  	Standard YAML parser	FLINK parser
  ConfigOption key	The key of a ConfigOption cannot be a prefix of another option's key.	No requirements.
  Comment	Comments must be separated from other tokens by white space characters.	Anything after the '#' symbol is considered a comment.
  Null value	Parses null or blank values as null.	Anything after the first ':' symbol is treated as a string type value, except for blank values.
  Indicator character	When using an indicator character as part of a string value, it is necessary to escape it in quotes to indicate that it is a string type. The indicator characters in standard YAML are as follows: - ? : , [ ] { } # & * ! | > ' " % @	No requirements.

  
  

• Deprecation:

  The old configuration file "flink-conf.yaml" will be deprecated by announcing this change in the release notes and user documentation.

• Migration Plan:

  In FLINK-2.0, the old parser will no longer be supported, nor will the flink-conf.yaml file be used as a configuration file.

...