[
https://issues.apache.org/jira/browse/FLINK-27676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huang Xingbo updated FLINK-27676:
---------------------------------
Affects Version/s: 1.14.4
> Output records from on_timer are behind the triggering watermark in PyFlink
> ---------------------------------------------------------------------------
>
> Key: FLINK-27676
> URL: https://issues.apache.org/jira/browse/FLINK-27676
> Project: Flink
> Issue Type: Bug
> Components: API / Python
> Affects Versions: 1.15.0, 1.14.4
> Reporter: Juntao Hu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
> Currently, when dealing with watermarks in AbstractPythonFunctionOperator,
> super.processWatermark(mark) is called, which advances watermark in
> timeServiceManager thus triggering timers and then emit current watermark.
> However, timer triggering is not synchronous in PyFlink (processTimer only
> put data into beam buffer), and when remote bundle is closed and output
> records produced by on_timer function finally arrive at Java side, they are
> already behind the triggering watermark.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
