[
https://issues.apache.org/jira/browse/FLINK-16326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050893#comment-17050893
]
Tzu-Li (Gordon) Tai commented on FLINK-16326:
---------------------------------------------
That indeed does look like a good direction for centralizing validation of
configs.
In StatefulFunction's scenario though, the problem is that some configs, like
{{execution.checkpointing.max-concurrent-checkpoints}} is strictly required to
be set to 1, because statefun currently doesn't support concurrent checkpoints.
I think that's not what the use case that
{{ConfigOption.withValidator(OptionValidator)}} was targeting at in the first
place, where there is some user-space validation.
None the less, I think FLINK-54 is good to have.
> 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
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
