BigData / Apache StreamPark Interview questions
What is the difference between StreamPark's HOCON config support and Flink's default flink-conf.yaml?
Both describe configuration, but they differ in expressiveness and where they apply.
flink-conf.yaml is Flink's own flat YAML configuration file — key-value settings that apply cluster- or job-wide, written in plain YAML with limited structuring. StreamPark added HOCON (Human-Optimized Config Object Notation) support as an alternative way to express a job's configuration, layered on top of what Flink itself accepts.
HOCON brings features flat YAML doesn't: comments that survive parsing more predictably, substitutions and variable references within the config itself, easy merging of multiple config fragments, and a more forgiving syntax for nested structures. For a StreamPark job with a lot of custom parameters, this makes the configuration easier to read, template, and reuse across similar jobs, while Flink's own flink-conf.yaml remains the baseline the cluster itself always understands.
More Related questions...