[
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 stale-minor (was: auto-deprioritized-critical
auto-deprioritized-major 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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, 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: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> auto-unassigned, stale-minor
>
> 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.20.1#820001)
