You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/05/21 00:54:03 UTC

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

     [ 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-unassigned stale-critical  (was: auto-unassigned)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Critical but is unassigned and neither itself nor its Sub-Tasks have been updated for 7 days. I have gone ahead and marked it "stale-critical". If this ticket is critical, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Critical
>              Labels: auto-unassigned, stale-critical
>
> 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)