flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] zhuzhurk opened a new pull request #9948: [FLINK-14451][runtime] Refactor FailoverTopology to extend base topology
Date Mon, 21 Oct 2019 05:08:08 GMT
zhuzhurk opened a new pull request #9948: [FLINK-14451][runtime] Refactor FailoverTopology
to extend base topology
URL: https://github.com/apache/flink/pull/9948
   ## What is the purpose of the change
   This PR is to change FailoverTopology to extend the base topology introduced in FLINK-14330.
ExecutionGraphToSchedulingTopologyAdapter(default implementation of SchedulingTopology) is
also to implement the FailoverTopology and replace DefaultFailoverTopology.
   More details see FLINK-14330.
   ## Brief change log
     - *Change FailoverTopology to extend the base topology and unifying the interfaces*
     - *Refactored the implementations of FailoverTopology*
     - *Refactored the usages of SchedulingTopology*
   ## Verifying this change
   This change is already covered by existing tests, such as ExecutionGraphToSchedulingTopologyAdapterTest*.
   ## Does this pull request potentially affect one of the following parts:
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes
/ **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing,
Yarn/Mesos, ZooKeeper: (**yes** / no / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   ## Documentation
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not

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:

With regards,
Apache Git Services

View raw message