[ 
https://issues.apache.org/jira/browse/FLINK-22425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-22425:
-----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: 
auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> allowedLateness and sideOutput not having an effect
> ---------------------------------------------------
>
>                 Key: FLINK-22425
>                 URL: https://issues.apache.org/jira/browse/FLINK-22425
>             Project: Flink
>          Issue Type: Bug
>          Components: API / DataStream
>            Reporter: Matthias
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> A user reported an issue [on the user 
> ML|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/event-time-window-cannot-become-earlier-than-the-current-watermark-by-merging-td43128.html#a43141]
>  where {{allowedLateness}} and {{sideOutput}} were applied to the Flink job, 
> apparently, without having an effect on late events.
> Adding dedicated filters solved it for him. See the [ML 
> thread|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/event-time-window-cannot-become-earlier-than-the-current-watermark-by-merging-td43128.html#a43141]
>  for code examples.
> A similar issue was reported on 
> [StackOverflow|https://stackoverflow.com/questions/57334257/the-end-timestamp-of-an-event-time-window-cannot-become-earlier-than-the-current].



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

Reply via email to