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 2016/08/17 17:38:20 UTC

[jira] [Resolved] (FLINK-4322) Unify CheckpointCoordinator and SavepointCoordinator

     [ https://issues.apache.org/jira/browse/FLINK-4322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Ewen resolved FLINK-4322.
---------------------------------
    Resolution: Fixed
      Assignee: Stephan Ewen

Fixed via 76ca1a7955fedd8583a0af12289a14d0f1bcf868 and 47acdeadf3ccd326578306453dd10ed3c147a4e6

> Unify CheckpointCoordinator and SavepointCoordinator
> ----------------------------------------------------
>
>                 Key: FLINK-4322
>                 URL: https://issues.apache.org/jira/browse/FLINK-4322
>             Project: Flink
>          Issue Type: Improvement
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.1.0
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.2.0
>
>
> The Checkpoint coordinator should have the functionality of both handling checkpoints and savepoints.
> The difference between checkpoints and savepoints is minimal:
>   - savepoints always write the root metadata of the checkpoint
>   - savepoints are always full (never incremental)
> The commonalities are large
>   - jobs should be able to resume from checkpoint or savepoints
>   - jobs should fall back to the latest checkpoint or savepoint
> This subsumes issue https://issues.apache.org/jira/browse/FLINK-3397



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)