[jira] [Created] (FLINK-13754) Decouple OperatorChain from StreamStatusMaintainer

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-13754) Decouple OperatorChain from StreamStatusMaintainer

Shang Yuanchun (Jira)
zhijiang created FLINK-13754:
--------------------------------

             Summary: Decouple OperatorChain from StreamStatusMaintainer
                 Key: FLINK-13754
                 URL: https://issues.apache.org/jira/browse/FLINK-13754
             Project: Flink
          Issue Type: Sub-task
          Components: Runtime / Task
            Reporter: zhijiang
            Assignee: zhijiang


There are two motivations for this refactoring:
 * It is the precondition for the following work of decoupling the dependency between two inputs status in ForwardingValveOutputHandler.
 * From the aspect of design rule, the current OperatorChain takes many unrelated roles like StreamStatusMaintainer to make it unmaintainable. The root reason for this case is from the cycle dependency between RecordWriterOutput (created by OperatorChain) and  StreamStatusMaintainer.

The solution is to refactor the creation of StreamStatusMaintainer and RecordWriterOutput in StreamTask level, and then break the implementation cycle dependency between them. The array of RecordWriters which has close relationship with RecordWriterOutput is created in StreamTask, so it is reasonable to create them together. The created StreamStatusMaintainer in StreamTask can be directly referenced by subclasses like OneInputStreamTask/TwoInputStreamTask.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)