Github user aljoscha commented on the issue:
    @StephanEwen we can do that but then we won't have any sanity checks for 
the `TypeSerializer` any more. Right now, even the RocksDB backed will 
serializer the `TypeSerializer`/`StateDescriptor` with the checkpoint to verify 
that the user only accesses it with the correct 
    I would be in favor of completely getting rid of user code there, even if 
it means losing those checks. Also, for this to work with the Heap backend we 
need to either always keep state on the heap in serialized form or deserialize 
lazily from restored serialized values using the `TypeSerializer` that we get 
from the user when they access state for the first time. 

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to