I am not really sure you can do that out of the box, if not, indeed that should be possible in the near future.
https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/stream/state.html#handling-serializer-upgrades-and-compatibility There are already plans for state migration (with upgraded serializers) as I read here, so this could be an additional task while migrating states, although I am not sure how easy or difficult this could be. Also, as you can read here, http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Evolving-serializers-and-impact-on-flink-managed-states-td14777.html Stefan really nicely explained what would/is happening on state migration on different backends. So based on that, what I can imagine is moving from FsStateBackend to RocksDbStateBackend or from MemoryStateBackend to RocksDbStateBackend would be easier, but not the other way round. Thanks -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Change-state-backend-tp14928p14961.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
