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/11/25 04:22:00 UTC

[jira] [Created] (FLINK-20335) Remove support for eager state specifications in module YAML definitions

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

             Summary: Remove support for eager state specifications in module YAML definitions
                 Key: FLINK-20335
                 URL: https://issues.apache.org/jira/browse/FLINK-20335
             Project: Flink
          Issue Type: Sub-task
          Components: Stateful Functions
            Reporter: Tzu-Li (Gordon) Tai
             Fix For: statefun-2.3.0


With FLINK-20265, we now support declaring state in StateFun functions, and that can change dynamically without any system downtime.

It can be confusing for users if we continued to support the legacy way of statically declaring state specifications in the module YAML definitions.

Therefore, we propose to completely remove that by:
* No longer support module YAML format versions <= 2.0.
* Remove the {{PersistedRemoteFunctionValues}} constructor that accepts a list of eager state specifications

This would be a breaking change:
* Users upgrading to version 2.3.0 have to rewrite their module YAMLs to conform to format version 3.0
* They also have to correspondingly update their functions to use SDKs of version 2.3.0.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)