[ 
https://issues.apache.org/jira/browse/FLINK-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512765#comment-15512765
 ] 

ASF GitHub Bot commented on FLINK-4603:
---------------------------------------

Github user aljoscha commented on the issue:

    https://github.com/apache/flink/pull/2533
  
    @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. 


> 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)

Reply via email to