TsReaper opened a new pull request #13625:
URL: https://github.com/apache/flink/pull/13625


   ## What is the purpose of the change
   
   Deadlock breakup algorithm and Multi-input operator creation algorithm need 
information about the input edges of an exec node, for example what's the 
priority of this input, and how the input records will trigger the output 
records.
   
   Although `BatchExecNode` currently has a `getDamBehavior` method, it only 
describes the behavior of the node and is not very useful for the new deadlock 
breakup algorithm. So we're going to introduce a new class `ExecEdge` to 
describe this and a new method `getInputEdges` for `ExecNode`.
   
   Current implementation of `getInputEdges` for `ExecNode`s is a collection 
and rewrite of current code (mostly from the `getDamBehavior`) without any test 
coverage. `getInputEdges` will be called when we introduce the new deadlock 
breakup and multi-input operator creation algorithm and will be tested along 
with the algorithm.
   
   ## Brief change log
   
    - Introduce `ExecEdge`
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ## 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:
us...@infra.apache.org


Reply via email to