[
https://issues.apache.org/jira/browse/FLINK-38321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruan Hang updated FLINK-38321:
------------------------------
Fix Version/s: 2.3.0
(was: 2.2.0)
> Optimize the timer registration logic n window early/late firing scenarios
> --------------------------------------------------------------------------
>
> Key: FLINK-38321
> URL: https://issues.apache.org/jira/browse/FLINK-38321
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 2.0.0, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0,
> 2.1.0
> Reporter: Jacky Lau
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> *Optimize the timer registration logic in window early/late firing scenarios.
> For keys that will not receive subsequent data, it is unnecessary to
> repeatedly register processing timers, thereby reducing the number of timers
> and state access to improve performance.*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
