You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Tzu-Li (Gordon) Tai (Jira)" <ji...@apache.org> on 2020/02/28 07:11:00 UTC

[jira] [Created] (FLINK-16326) Eagerly validate strictly required Flink configurations for Stateful Functions

Tzu-Li (Gordon) Tai created FLINK-16326:
-------------------------------------------

             Summary: 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


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)