You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2021/08/24 13:47:00 UTC

[jira] [Commented] (FLINK-23808) Bypass operators when advanceToEndOfEventTime for both legacy and new source tasks

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

Piotr Nowojski commented on FLINK-23808:
----------------------------------------

{quote}
like WatermarkAssignerOperator, which might cause problems.
{quote}
[~gaoyunhaii], can you elaborate what problems did you mean? I presume this was discovered by our WIP ITCase?

> Bypass operators when advanceToEndOfEventTime for both legacy and new source tasks
> ----------------------------------------------------------------------------------
>
>                 Key: FLINK-23808
>                 URL: https://issues.apache.org/jira/browse/FLINK-23808
>             Project: Flink
>          Issue Type: Sub-task
>    Affects Versions: 1.14.0
>            Reporter: Yun Gao
>            Assignee: Yun Gao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.14.0
>
>
> Currently when end of data processing, the sources would advance to max watermark and emit MAX_WATERMARK. However, currently the output used is the mainOperatorOutput, namely the output of the source operator. If the source operator is chained with other operators and the tasks are finished on restore, there would be problems  since the following operators should be skipped, but some operators still have actions when the watermark is advanced, like WatermarkAssignerOperator, which might cause problems.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)