[
https://issues.apache.org/jira/browse/FLINK-16326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047293#comment-17047293
]
Dawid Wysakowicz commented on FLINK-16326:
------------------------------------------
Big +1 for eager validation. I think whole Flink project could benefit from
eager validation of ConfigOptions. We tried to introduce that before. You can
see some of our thoughts here:
https://cwiki.apache.org/confluence/display/FLINK/FLIP-54%3A+Evolve+ConfigOption+and+Configuration#FLIP-54:EvolveConfigOptionandConfiguration-OptionSetsandSetValidation
> Eagerly validate strictly required Flink configurations for Stateful Functions
> ------------------------------------------------------------------------------
>
> Key: FLINK-16326
> URL: https://issues.apache.org/jira/browse/FLINK-16326
> Project: Flink
> Issue Type: Improvement
> Components: Stateful Functions
> Affects Versions: statefun-1.1
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Critical
>
> Currently, when Stateful Functions users want to set their own Flink
> configurations, they are required to build on top of a base template
> {{flink-conf.yaml}} which has some strictly required configurations
> predefined, such as parent-first classloading and state backend settings.
> These Flink settings should never (as of now) be changed by the user, but
> there is no validation of that in place. We should do that eagerly
> pre-submission of the translated job, probably in {{StatefulFunctionsConfig}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
