Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/5885
A note about previous tests that should have been failing because of this
issue:
The tests
`StateBackendTestBase#testKryoRestoreResilienceWithDifferentRegistrationOrder()`
and
`StateBackendTestBase#testPojoRestoreResilienceWithDifferentRegistrationOrder`
was supposed to, to some extend, test serializer reconfigurations across
backend state restores.
f553d9b adds an extension to the Kryo test that verifies the state handles
actually uses the correct reconfigured serializer. After adding that extension,
the test fails without this PR.
However, that still doesn't explain why, especially in the RocksDB case,
modifications to the state did not cause errors while it was using the
non-reconfigured serializer (with outdated Kryo registration mappings).
---
