Details
-
Bug
-
Status: Resolved
-
P0
-
Resolution: Fixed
-
2.20.0
-
None
Description
With the introduction of timer output timestamp, a new watermark hold had been added to the Flink Runner. The watermark computation works on the keyed state backend which computes a key-scoped watermark hold and not the desired operator-wide watermark hold.
We need to change this to operate on all keys. This has to be done before fixing BEAM-9566.
Attachments
Issue Links
- is related to
-
BEAM-9566 Performance regression of FlinkRunner stream mode due to watermark holds update
- Resolved
- links to