[FLINK-20085] Remove RemoteFunctionStateMigrator from restore code paths #172
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
igalshilman
approved these changes
Nov 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
RemoteFunctionStateMigratorwas added in 2.2.x to allow migrating legacy multiplexed remote function state in versions < 2.2.0, to the new demultiplexed format starting from 2.2.Since the 2.2 series is now released and writes only in the new formats, we can now safely remove this migration path.
What this means for users that are still on StateFun versions < 2.2.0, if they want to upgrade to 2.3.x in the future:
Change log
RemoteFunctionStateMigratorand all its usagesstatefun.remote.migrate-legacy-state, which was introduced in the past as an internal flag for switching on the migration path, if users require it.