[ 
https://issues.apache.org/jira/browse/FLINK-20085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tzu-Li (Gordon) Tai updated FLINK-20085:
----------------------------------------
    Issue Type: Task  (was: Bug)

> Remove RemoteFunctionStateMigrator code paths from StateFun 
> ------------------------------------------------------------
>
>                 Key: FLINK-20085
>                 URL: https://issues.apache.org/jira/browse/FLINK-20085
>             Project: Flink
>          Issue Type: Task
>          Components: Stateful Functions
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Tzu-Li (Gordon) Tai
>            Priority: Blocker
>             Fix For: statefun-2.3.0
>
>
> The {{RemoteFunctionStateMigrator}} was added to allow savepoints with 
> versions <= 2.1.0 to have a migration path for upgrading to versions >= 
> 2.2.0. The binary format of remote function state was changed due to 
> demultiplexed remote state, introduced in 2.2.0.
> With 2.2.0 already released with the new formats, it is now safe to fully 
> remove this migration path.
> For users, what this means that it would not be possible to directly upgrade 
> from 2.0.x / 2.1.x to 2.3.x+. They'd have to perform incremental upgrades via 
> 2.2.x, by restoring first with 2.2.x and then taking another savepoint, 
> before upgrading to 2.3.x.



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

Reply via email to