[
https://issues.apache.org/jira/browse/FLINK-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek closed FLINK-5421.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Implemented on release-1.2 in:
39fc07f87edd33ee78459b2d08b9d767efb100cc
849f701ef1ebb149081e530dbca426b88795dd73
> Explicit restore method in Snapshotable
> ---------------------------------------
>
> Key: FLINK-5421
> URL: https://issues.apache.org/jira/browse/FLINK-5421
> Project: Flink
> Issue Type: Improvement
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Fix For: 1.2.0
>
>
> We should introduce an explicit {{restore(...)}} method to match the
> {{snapshot(...)}} method in this interface.
> Currently, restore happens implicit in backends, i.e. when state handles are
> provided, backends execute restore logic in their constructors. This
> behaviour makes it hard for backends to participate in the task's lifecycle
> through {{CloseableRegistry}}, because we can only register backend objects
> after they have been constructed. As a result, for example, all restore
> operations that happen in the constructor are not responsive to cancelation.
> When we introduce an explicit restore, we can first create a backend object,
> then register it, and only then run restore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
