[FLINK-16326] Eagerly validate strictly required Flink configurations for Stateful Functions

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: statefun-2.0.0
• Fix Version/s: statefun-2.0.0
• Component/s: Stateful Functions
• Labels: pull-request-available
• Assignee: Tzu-Li (Gordon) Tai
• Reporter: Tzu-Li (Gordon) Tai
• Created: 28/Feb/20 07:10
• Updated: 04/Mar/20 05:03
• Resolved: 04/Mar/20 05:03

Description

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.

Issue Links

• links to: GitHub Pull Request #47