flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aljoscha <...@git.apache.org>
Subject [GitHub] flink issue #2533: [FLINK-4603] Fixes: KeyedStateBackend cannot restore user...
Date Thu, 22 Sep 2016 09:36:42 GMT
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 `TypeSerializer`/`StateDescriptor`.
    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 infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message