[jira] [Created] (FLINK-6856) Eagerly check if serializer config snapshots are deserializable when snapshotting

["Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org>]

Tzu-Li (Gordon) Tai created FLINK-6856:
------------------------------------------

             Summary: Eagerly check if serializer config snapshots are deserializable when snapshotting
                 Key: FLINK-6856
                 URL: https://issues.apache.org/jira/browse/FLINK-6856
             Project: Flink
          Issue Type: Improvement
          Components: State Backends, Checkpointing
    Affects Versions: 1.3.0
            Reporter: Tzu-Li (Gordon) Tai
            Assignee: Tzu-Li (Gordon) Tai


Currently, if serializer config snapshots are not deserializable (for example, if the user did not correctly include the deserialization empty constructor, or the read / write methods are simply wrongly implemented), user's would only be able to find out this when restoring from the snapshot.

We could eagerly do a check for this when snapshotting, and fail with a good message indicating that the config snapshot can not be deserialized.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)