You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/02/26 15:57:00 UTC

[jira] [Closed] (FLINK-2250) Backtracking of intermediate results

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

Till Rohrmann closed FLINK-2250.
--------------------------------
    Resolution: Incomplete

I think we should rethink this issue with streaming in mind.

> Backtracking of intermediate results
> ------------------------------------
>
>                 Key: FLINK-2250
>                 URL: https://issues.apache.org/jira/browse/FLINK-2250
>             Project: Flink
>          Issue Type: New Feature
>          Components: DataSet API, Distributed Coordination
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Major
>
> With intermediate results available in the distributed runtime as of FLINK-986, we could now incrementally resume failed jobs if we cached the results FLINK-1404. Moreover, Flink users could build incremental Flink jobs using count/collect/print and, ultimately, also continue from old job results in an interactive shell environment like the scala-shell.
> The following tasks need to be completed for that to happen:
> - Cache the results
> - Keep the ExecutionGraph in the JobManager
> - Change the scheduling mechanism to track back the results from the sinks
> - Implement a session management to eventually discard old results and ExecutionGraphs from the TaskManagers/JobManager 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)