XComp opened a new pull request #14804: URL: https://github.com/apache/flink/pull/14804
## What is the purpose of the change We want to forward the exception history (see [FLINK-6042](https://issues.apache.org/jira/browse/FLINK-6042)) as part of a wrapper class. This enables us to extend the objects passed forward to the history server and ExecutionGraph processing REST handlers more easily (considering possible changes here in the context of the declarative scheduler work in [FLIP-160](https://cwiki.apache.org/confluence/display/FLINK/FLIP-160%3A+Declarative+Scheduler)). ## Brief change log * Initially, I introduced `WithExecutionGraph` and `WithExceptionHistory` as separate interfaces. I would oppose this decision now due to the way the `ExecutionGraphInfo` is used. * `ExecutionGraphInfo` replaces almost all occurrences of `ArchivedExecutionGraph`. * `AbstractArchivedExecutionGraphHandler` is introduced to have all subclasses of the old `AbstractExecutionGraphHandler` (except for `JobExceptionsHandler`) use this new abstract parent class, instead. * The `JsonArchivist` was extended by a default implementation handling `ExecutionGraphInfo`. ## Verifying this change No functionality is changed. All present test should still pass. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
