Andrey Zagrebin created FLINK-12530:
---------------------------------------

             Summary: Move Task.inputGatesById to NetworkEnvironment
                 Key: FLINK-12530
                 URL: https://issues.apache.org/jira/browse/FLINK-12530
             Project: Flink
          Issue Type: Sub-task
          Components: Runtime / Network
            Reporter: Andrey Zagrebin
            Assignee: Andrey Zagrebin
             Fix For: 1.9.0


Task.inputGatesById indexes SingleInputGates by id. The end user of this 
indexing is NetworkEnviroment for two cases:

- SingleInputGate triggers producer partition readiness check and then the 
successful result of check is dispatched back to this SingleInputGate by id. We 
can just add an additional argument to 
TaskActions.triggerPartitionProducerStateCheck. The argument is an immediate 
callback to that SingleInputGate. Then inputGatesById is not needed for 
dispatching.

- TaskExecutor.updatePartitions uses inputGatesById to dispatch PartitionInfo 
update to the right SingleInputGate. If inputGatesById is moved to 
NetworkEnviroment, which should be a better place for gate management, and add 
NetworkEnviroment.updatePartitionInfo then TaskExecutor.updatePartitions could 
directly call NetworkEnviroment.updatePartitionInfo.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to