[
https://issues.apache.org/jira/browse/FLINK-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323644#comment-17323644
]
Flink Jira Bot commented on FLINK-6856:
---------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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: Runtime / State Backends
> Affects Versions: 1.3.0, 1.4.2, 1.5.1, 1.6.0
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Priority: Critical
> Labels: stale-assigned
>
> 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
(v8.3.4#803005)
