You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/02/25 23:00:00 UTC
[jira] [Resolved] (FLINK-16192) Remove "Legacy State" and
Checkpoint Compatibility with Flink 1.2
[ https://issues.apache.org/jira/browse/FLINK-16192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-16192.
----------------------------------
Resolution: Fixed
Fixed in 1.11.0 via b8277f92cfd1fa80325194bd705d1a13293b30e3
> Remove "Legacy State" and Checkpoint Compatibility with Flink 1.2
> -----------------------------------------------------------------
>
> Key: FLINK-16192
> URL: https://issues.apache.org/jira/browse/FLINK-16192
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Major
> Fix For: 1.11.0
>
>
> Legacy state is state produced by the {{Checkpointed}} interface, back in the days before Flink applications were re-scalable. The interface was deprecated in Flink 1.2, support dropped in Flink 1.4.
> Removing legacy state leads to a lot of nice cleanups and simplifications in the code, especially in the checkpoint metadata handling. This was in fact the motivation, extending checkpoints to include "operator coordinators".
> Removing support for this is in theory independent of removing support for Flink 1.2, but in practice all the testing savepoints for 1.2 compatibility use still this state. Dropping "legacy state" means either some very involved reworking of all the 1.2 compatibility tests and re-building the 1.2 snapshots, or dropping compatibility with Flink 1.2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)