[
https://issues.apache.org/jira/browse/FLINK-38216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rui Fan resolved FLINK-38216.
-----------------------------
Fix Version/s: 2.2.0
Resolution: Fixed
Merged to master(2.2.0) via: c9773f411e7c8aab01f875877820a788a079828b
> Refactor EndOfChannelStateEvent according to input buffer and output buffer
> ---------------------------------------------------------------------------
>
> Key: FLINK-38216
> URL: https://issues.apache.org/jira/browse/FLINK-38216
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> {color:#292a2e}Both of input buffers and out buffers use the same
> EndOfChannelStateEvent, but it is used in different way.{color}
> {color:#292a2e}For {color:#292a2e}EndOfChannelStateEvent{color} of input
> buffer (downstream task side):{color}
> * It is emitted by the downstream after emitting the last recovered input
> buffer for a channel
> * this triggers that input channel conversion to a “normal channel”
> {color:#292a2e}For {color:#292a2e}EndOfChannelStateEvent{color} of output
> buffer (upstream task side):{color}
> * it is emitted by the upstream after sending the last recovered output
> buffer
> * this eventually triggers task input conversion in the downstream to a
> “normal input”
>
> The code would be more clearer if this event is separated into 2 events, like:
> * EndOfInputChannelStateEvent and EndOfOutputChannelStateEvent
> * EndOfUpstreamChannelStateEvent and EndOfDownstreamChannelStateEvent
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
