You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/03/29 11:05:00 UTC

[jira] [Commented] (FLINK-26708) TimestampsAndWatermarksOperator should not propagate WatermarkStatus

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

Chesnay Schepler commented on FLINK-26708:
------------------------------------------

I reverted the changes on the 1.13 branch as the WatermarkStatus doesn't exist on that branch and it was breaking the build.

> TimestampsAndWatermarksOperator should not propagate WatermarkStatus
> --------------------------------------------------------------------
>
>                 Key: FLINK-26708
>                 URL: https://issues.apache.org/jira/browse/FLINK-26708
>             Project: Flink
>          Issue Type: Bug
>          Components: API / DataStream
>    Affects Versions: 1.15.0, 1.14.4
>            Reporter: Dawid Wysakowicz
>            Assignee: Dawid Wysakowicz
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0, 1.14.5
>
>
> The lifecycle/scope of WatermarkStatus is tightly coupled with watermarks. Upstream watermarks are cut off in the TimestampsAndWatermarksOperator and therefore watermark statuses should be cut off as well.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)