[
https://issues.apache.org/jira/browse/FLINK-17208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245683#comment-17245683
]
Yingjie Cao commented on FLINK-17208:
-------------------------------------
[~AHeise] This ticket was created for FLINK-16641. The code base has changed a
lot since then, I am not sure whether this change is needed. I will try to
confirm that and if this change is not needed, I will close this ticket then.
BTW, I have removed the fix version.
> Reduce redundant data available notification of PipelinedSubpartition
> ---------------------------------------------------------------------
>
> Key: FLINK-17208
> URL: https://issues.apache.org/jira/browse/FLINK-17208
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Network
> Affects Versions: 1.11.0
> Reporter: Yingjie Cao
> Assignee: Yingjie Cao
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are three scenarios that may lead to redundant data available
> notifications for PipelinedSubpartition:
> # Add a new BufferConsumer after an event;
> # Finish the current subpartition;
> # Flush an event buffer.
> We can avoid these redundant data available notifications.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
