kl0u opened a new pull request #13649:
URL: https://github.com/apache/flink/pull/13649


   ## What is the purpose of the change
   
   Currently, the `StreamGraphGenerator` is responsible for:
   1. traversing the graph of `Transformations`
   2. translating them to their runtime implementations
   
   With the addition of the `TransformationTranslator` framework in 
[FLINK-19485](https://issues.apache.org/jira/browse/FLINK-19485), we can now 
pull the translation logic out of the `StreamGraphGenerator` and put it into 
dedicated translators, one for each type of transformation.
   
   This PR does so for the:
   
   * SideOutputTransformation
   * PartitionTransformation 
   * UnionTransformation 
   * LegacySourceTransformation 
   * LegacySinkTransformation 
   * SourceTransformation
   
   ## Brief change log
   
   The changes are in the `StreamGraphGenerator` and the individual 
`TransformationTranslator` 's.
   
   ## Verifying this change
   
   This change is a (big) code cleanup and does not introduce any new features, 
so it is expected to be covered by existing tests.
   
   ## 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, Kubernetes/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 documented)
   


----------------------------------------------------------------
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]


Reply via email to