[
https://issues.apache.org/jira/browse/BEAM-9733?focusedWorklogId=425391&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-425391
]
ASF GitHub Bot logged work on BEAM-9733:
----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Apr/20 17:24
Start Date: 20/Apr/20 17:24
Worklog Time Spent: 10m
Work Description: tweise commented on issue #11362:
URL: https://github.com/apache/beam/pull/11362#issuecomment-616698674
I will take another pass shortly, but overall the changes look good. With
the improved test coverage, we will be more confident that future modifications
don't break the watermark handling. Given the scope of changes, it would be
good to put this through regression testing with a real application.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 425391)
Time Spent: 8h (was: 7h 50m)
> ImpulseSourceFunction does not emit a final watermark
> -----------------------------------------------------
>
> Key: BEAM-9733
> URL: https://issues.apache.org/jira/browse/BEAM-9733
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Critical
> Fix For: 2.21.0
>
> Time Spent: 8h
> Remaining Estimate: 0h
>
> The Flink Runner's {{ImpulseSourceFunction}} does not emit a final watermark,
> unless {{--shutdownSourcesOnFinalWatermark}} flag has been specified (the
> flag is used in tests to shutdown the pipeline after reading all data). Most
> pipelines will be long-running and thus do not specify the flag.
> Not sending out the final watermark causes GroupByKey to hold back the data
> of event time windows until the pipeline is shut down (the final watermark is
> always emitted on pipeline shutdown which is why using the above flag works).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
