godfreyhe opened a new pull request #14757:
URL: https://github.com/apache/flink/pull/14757


   
   ## What is the purpose of the change
   
   *Currently, the ExecEdge represents the properties for the input of an 
operator, the properties include
   1. required data distribute for an input (the input corresponds to the 
[Input](https://github.com/apache/flink/blob/master/flink-streaming-java/src/main/java/org/apache/flink/streaming/api/operators/Input.java))
   2. DamBehavior which describes the behaviors how an in record may trigger 
the output of the target operator.
   3. the priority of this input read by the target operator
   
   So ExecEdge should be rename to InputProperty, and we will re-introduce 
ExecEdge which describes how to connect two ExecNodes in FLINK-21150, and how 
to shuffle the data between two ExecNodes. Its role should be similar to 
StreamEdge.*
   
   
   ## Brief change log
   
     - *Rename ExecEdge to InputProperty*
     - *rename RequiredShuffle to RequiredDistribution*
   
   
   ## Verifying this change
   
   This change is a refactoring rework 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:
us...@infra.apache.org


Reply via email to