[
https://issues.apache.org/jira/browse/FLINK-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512855#comment-15512855
]
ASF GitHub Bot commented on FLINK-4603:
---------------------------------------
Github user StefanRRichter commented on the issue:
https://github.com/apache/flink/pull/2533
@StephanEwen at least in the RocksDB backend we could remove user code
completely. Right now, the only thing that needs to be serialized is the
TypeSerializer from the ValueDescriptor. It is used in a check that users can
not provide a descriptor with a different TypeSerializer than the one that was
used initially. We might think about removing this to support versioning of
TypeSerializers, but how can we somehow enforce compatibility between them?
> KeyedStateBackend cannot restore user code classes
> --------------------------------------------------
>
> Key: FLINK-4603
> URL: https://issues.apache.org/jira/browse/FLINK-4603
> Project: Flink
> Issue Type: Bug
> Components: State Backends, Checkpointing
> Affects Versions: 1.2.0
> Reporter: Till Rohrmann
> Assignee: Stefan Richter
> Priority: Blocker
> Fix For: 1.2.0
>
>
> A user reported that he cannot restore keyed state which contains user code
> classes. I suspect that we don't use the user code class loader to
> deserialize the state.
> The solution seems to be to forward the user code class loader to the
> {{KeyedStateBackends}} when restoring state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
