[
https://issues.apache.org/jira/browse/FLINK-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6856:
----------------------------------
Labels: auto-deprioritized-critical auto-deprioritized-major
auto-unassigned (was: auto-deprioritized-critical auto-unassigned stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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
> Priority: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> auto-unassigned
>
> 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)
