[
https://issues.apache.org/jira/browse/BEAM-11481?focusedWorklogId=525490&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-525490
]
ASF GitHub Bot logged work on BEAM-11481:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Dec/20 10:59
Start Date: 17/Dec/20 10:59
Worklog Time Spent: 10m
Work Description: dmvk commented on pull request #13571:
URL: https://github.com/apache/beam/pull/13571#issuecomment-747368390
My best guess is that impulse progresses input WM from MIN to MAX and we let
watermark hold to handle the progression... in that case, SDF probably never
worked properly on flink runner 🤔
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 525490)
Time Spent: 40m (was: 0.5h)
> FlinkRunner might not advance output watermark on change of watermark hold
> --------------------------------------------------------------------------
>
> Key: BEAM-11481
> URL: https://issues.apache.org/jira/browse/BEAM-11481
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.26.0
> Reporter: Jan Lukavský
> Assignee: Jan Lukavský
> Priority: P0
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Output watermark of DoFnOperator is advanced only when new input watermark is
> received. The output watermark might advance even on timer or processed
> element due to updated watermark hold. This especially holds true in
> splittable DoFn.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
