[
https://issues.apache.org/jira/browse/FLINK-26063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Khachatryan resolved FLINK-26063.
---------------------------------------
Resolution: Fixed
Merged into 1.15 as e31c1b0f88cbcd3f3a720948123b262fc21e4cd5 and into master as
092647cb3db6dcdf43fbf4a04b9f6cd5a95bee79.
> [Changelog] Incorrect key group logged for PQ.poll and remove
> -------------------------------------------------------------
>
> Key: FLINK-26063
> URL: https://issues.apache.org/jira/browse/FLINK-26063
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
> Affects Versions: 1.15.0
> Reporter: Roman Khachatryan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0, 1.16.0
>
>
> Key group is logged so that state changes can be re-distributed or shuffled.
> It is currently obtained from keyContext during poll() and remove()
> operations.
> However, keyContext is not updated when dequeing processing time timers.
> The impact is relatively small for remove(): in the worst case, the operation
> will be ignored.
> poll() should probably be replaced with remove() anyways - see FLINK-26062.
> One way to solve this problem is to extract key group from the polled element
> - if it is a timer.
> cc: [~masteryhx], [~ym], [~yunta]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
