[
https://issues.apache.org/jira/browse/FLINK-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562255#comment-15562255
]
ASF GitHub Bot commented on FLINK-4720:
---------------------------------------
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2577
>I am using the ExecutionConfigSummary (and removed my original
ArchivedExecutionConfig) when i rebased, so I'm not sure what you mean :/
That's what I meant, I wondered why you didn't use your archive design
pattern for `ExecutionConfig`.
What do you think about the `Archiveable<T extends Serializable>` interface
I proposed?
> Implement an archived version of the execution graph
> ----------------------------------------------------
>
> Key: FLINK-4720
> URL: https://issues.apache.org/jira/browse/FLINK-4720
> Project: Flink
> Issue Type: Improvement
> Components: JobManager, Webfrontend
> Affects Versions: 1.1.2
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Fix For: 1.2.0
>
>
> In order to implement a job history server, as well as separate the
> JobManager from the WebInterface, we require an archived version of the
> ExecutionGraph that is Serializable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
