[
https://issues.apache.org/jira/browse/FLINK-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhijiang updated FLINK-13754:
-----------------------------
Summary: Decouple OperatorChain with StreamStatusMaintainer (was: Decouple
OperatorChain from StreamStatusMaintainer)
> Decouple OperatorChain with 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The current OperatorChain is heavy-weight to take some unrelated roles like
> StreamStatusMaintainer. If other components only rely on the
> StreamStatusMaintainer, we have to pass the whole OperatorChain. From the
> design aspect of single function, we need to decouple
> 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
(v8.3.2#803003)
