[ 
https://issues.apache.org/jira/browse/FLINK-11286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776586#comment-16776586
 ] 

Tzu-Li (Gordon) Tai edited comment on FLINK-11286 at 2/25/19 7:35 AM:
----------------------------------------------------------------------

Regarding limitation to source DOP if watermark assignment needs to strictly 
happen only at the source and not mid-pipeline:
that is indeed a fair argument. [~aljoscha] what do you think about this one?


was (Author: tzulitai):
Regarding limitation to source DOP if watermark assignment happens strictly at 
the source and not mid-pipeline:
that is indeed a fair argument. [~aljoscha] what do you think about this one?

> Support to send StreamStatus.IDLE for non-source operators 
> -----------------------------------------------------------
>
>                 Key: FLINK-11286
>                 URL: https://issues.apache.org/jira/browse/FLINK-11286
>             Project: Flink
>          Issue Type: Improvement
>          Components: DataStream API
>            Reporter: vinoyang
>            Assignee: vinoyang
>            Priority: Major
>
> Currently, only stream source tasks can be marked as temporary idle. But many 
> times, this approach has limitations.
> Considering such a scenario, there is a DAG as follows: 
> {{source->map->filter->flatmap->keyBy->window}}, with a degree of parallelism 
> of 10. Among them, the watermark is not sent by the source operator, but is 
> downstream, such as flatmap. Every source subtask will not be idle. However, 
> after the filter, some pipelines generate "idle". For example, there are 3 
> pipelines that will no longer have data sent downstream. At this time, we 
> can't call the {{markAsTemporarilyIdle}} method to mark the current pipeline 
> in the idle state. This will affect the downstream window.



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

Reply via email to