GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/6325
[FLINK-9376] Allow upgrading to incompatible state serializers (state
schema evolution)
This is WIP so people can have a look.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink jira-9376-state-upgrade
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/6325.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #6325
----
commit 5fc4a36a144c3f8f22be7e21a4e542d3042d10b1
Author: Tzu-Li (Gordon) Tai <tzulitai@...>
Date: 2018-06-13T11:43:53Z
[FLINK-9377] [core] (part 1) Extend TypeSerializerConfigSnapshot as a
factory for restoring serializers
This commit is the first step towards removing serializers from
checkpointed state meta info and making Flink checkpoints Java
serialization free.
Instead of writing serializers in checkpoints, and trying to read that
to obtain a restore serializer at restore time, we aim to only write the
config snapshot as the single source of truth and use it as a factory to
create a restore serializer.
This commit adds the method and signatures to the
TypeSerializerConfigSnapshot interface. Use of the method, as well as
properly implementing the method for all serializers, will be
implemented in follow-up commits.
commit 661eb6d34da450ed096a77f166a4cc62ce3efdba
Author: Tzu-Li (Gordon) Tai <tzulitai@...>
Date: 2018-06-14T09:52:06Z
[FLINK-9377] [core] (part 2) Remove fallback deserializer option from
CompatibilityResult
Now that the config snapshot is used as a factory for the restore
serializer, it should be guaranteed that a restore serializer is always
available. This removes the need for the user to provide a "fallback"
convert serializer in the case where a migration is required.
commit c91d045c5eb6e355981e4edaa6d1a0d48e5d4a5e
Author: Tzu-Li (Gordon) Tai <tzulitai@...>
Date: 2018-06-14T14:41:45Z
[FLINK-9377] [core] (part 3) Deprecate TypeSerializerSerializationUtil
This commit deprecates all utility methods and classes related to
serializing serializers. All methods that will still be in use, i.e.
writing config snapshots, are now moved to a separate new
TypeSerializerConfigSnapshotSerializationUtil class.
commit e09f91469fb6c86f5d2f05b78a9db3d9af8cce87
Author: Tzu-Li (Gordon) Tai <tzulitai@...>
Date: 2018-06-18T14:24:08Z
[FLINK-9377] [core] (part 4) Introduce BackwardsCompatibleConfigSnapshot
The BackwardsCompatibleConfigSnapshot is a wrapper, dummy config
snapshot which wraps an actual config snapshot, as well as a
pre-existing serializer instance.
In previous versions, since the config snapshot wasn't a serializer
factory but simply a container for serializer parameters, previous
serializers didn't necessarily have config snapshots that are capable of
correctly creating a correct corresponding restore serializer.
In this case, since previous serializers still have serializers written
in the checkpoint, the backwards compatible solution would be to wrap
the written serializer and the config snapshot within the
BackwardsCompatibleConfigSnapshot dummy. When attempting to restore the
serializer, the wrapped serializer instance is returned instead of
actually calling the restoreSerializer method of the wrapped config
snapshot.
commit da84665a9b101a803f7446210afc34bbd4a71703
Author: Tzu-Li (Gordon) Tai <tzulitai@...>
Date: 2018-07-02T03:45:20Z
[FLINK-9377] [core] (part 5) Remove serializers from checkpoint state meta
infos
This commit officially removes the behaviour of writing serializers in
the state meta info of keyed state, operator state, and timers state.
This affects the serialization formats of the
KeyedBackendSerializationProxy, OperatorBackendSerializationProxy, and
InternalTimerServiceSerializationProxy, and therefore their versions are
all upticked.
commit ee583fdcfc920413f9ddd6b70bcb96e324124015
Author: Tzu-Li (Gordon) Tai <tzulitai@...>
Date: 2018-07-10T08:04:41Z
[FLINK-9377] (wip) Extend CompatibilityResult
commit 39d84472518d776c2c0aa575ec75eab8411cc512
Author: Tzu-Li (Gordon) Tai <tzulitai@...>
Date: 2018-07-10T09:49:25Z
[FLINK-9377] (wip) Move responsibility of compatibility checks to config
snapshot
commit 53242ec674cc35f2abc881e48e1a07098b2b913c
Author: Tzu-Li (Gordon) Tai <tzulitai@...>
Date: 2018-06-18T14:24:35Z
[FLINK-9377] [core] (part 6) Properly implement restoreSerializer for
simple composite serializer config snapshots
commit 89c8b1ab30fa8d92eb9cb9813bdd98ebfc4fdccc
Author: Aljoscha Krettek <aljoscha.krettek@...>
Date: 2018-07-11T13:43:46Z
[FLINK-9376] Move resolveKvStateCompatibility functionality into state
backends
The heap backend and the RocksDB backend have different requirements:
for the heap backend we don't have to check serializer compatibility
since we always get state conversion for free because we read with the
old serializer and write the next snapshot with the new serializer. For
Rocks we need more fine-grained control, therefore we have to do the
checks (and conversions in a future commit) in the backend itself.
commit 30453b1d7d9c8c7c1d35fee190a4a85584603c3c
Author: Aljoscha Krettek <aljoscha.krettek@...>
Date: 2018-07-12T14:42:26Z
[FLINK-9376] Update version in StateTableByKeyGroupReaders
commit 865f529907ee144e6f7a637f6efd1585d9ea8586
Author: Aljoscha Krettek <aljoscha.krettek@...>
Date: 2018-07-11T16:29:30Z
[FLINK-9376] Migrate RocksDB state when necessary
----
---
