[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-deprioritized-critical auto-deprioritized-major auto-deprioritized-minor auto-unassigned (was: auto-deprioritized-critical auto-deprioritized-major auto-unassigned stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, 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: Not a Priority > Labels: auto-deprioritized-critical, auto-deprioritized-major, > auto-deprioritized-minor, 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.20.1#820001)
[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-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)
[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-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)
[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-deprioritized-critical auto-unassigned stale-major (was: auto-deprioritized-critical 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 Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, 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: Major > Labels: auto-deprioritized-critical, auto-unassigned, stale-major > > 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)
[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-deprioritized-critical auto-unassigned (was: auto-unassigned stale-critical) Priority: Major (was: Critical) This issue was labeled "stale-critical" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Critical, 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: Major > Labels: auto-deprioritized-critical, 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)
[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)
[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 (was: stale-assigned) > 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 > > 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)
[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: stale-assigned (was: ) > 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)
[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 ] Till Rohrmann updated FLINK-6856: - Fix Version/s: (was: 1.7.0) > 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, 1.4.2, 1.5.1, 1.6.0 >Reporter: Tzu-Li (Gordon) Tai >Assignee: Tzu-Li (Gordon) Tai >Priority: Critical > Fix For: 1.8.0 > > > 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 (v7.6.3#76005)
[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 ] Till Rohrmann updated FLINK-6856: - Fix Version/s: 1.8.0 > 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, 1.4.2, 1.5.1, 1.6.0 >Reporter: Tzu-Li (Gordon) Tai >Assignee: Tzu-Li (Gordon) Tai >Priority: Critical > Fix For: 1.7.0, 1.8.0 > > > 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 (v7.6.3#76005)
[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 ] Till Rohrmann updated FLINK-6856: - Fix Version/s: (was: 1.6.0) 1.7.0 > 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, 1.4.2, 1.5.1, 1.6.0 >Reporter: Tzu-Li (Gordon) Tai >Assignee: Tzu-Li (Gordon) Tai >Priority: Critical > Fix For: 1.7.0 > > > 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 (v7.6.3#76005)
[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 ] Till Rohrmann updated FLINK-6856: - Affects Version/s: 1.6.0 1.4.2 1.5.1 > 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, 1.4.2, 1.5.1, 1.6.0 >Reporter: Tzu-Li (Gordon) Tai >Assignee: Tzu-Li (Gordon) Tai >Priority: Critical > Fix For: 1.7.0 > > > 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 (v7.6.3#76005)
[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 ] Aljoscha Krettek updated FLINK-6856: Fix Version/s: (was: 1.5.1) 1.6.0 > 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 >Priority: Critical > Fix For: 1.6.0 > > > 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 (v7.6.3#76005)
[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 ] Till Rohrmann updated FLINK-6856: - Fix Version/s: (was: 1.5.0) 1.5.1 > 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 >Priority: Critical > Fix For: 1.5.1 > > > 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 (v7.6.3#76005)
[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 ] Tzu-Li (Gordon) Tai updated FLINK-6856: --- Priority: Critical (was: Major) > 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 >Priority: Critical > Fix For: 1.5.0 > > > 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.4.14#64029)
[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 ] Tzu-Li (Gordon) Tai updated FLINK-6856: --- Fix Version/s: 1.5.0 > 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 > Fix For: 1.5.0 > > > 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.4.14#64029)
