You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Seth Wiesman (Jira)" <ji...@apache.org> on 2020/02/21 16:24:00 UTC
[jira] [Updated] (FLINK-16223) Flat aggregate misuses key group
ranges
[ https://issues.apache.org/jira/browse/FLINK-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Seth Wiesman updated FLINK-16223:
---------------------------------
Description:
The implementation of flat aggregate appears to misuse key group ranges. When we add a check in AbstractStreamOperator that the current key belongs to the key group assigned to that subtask, tests in TableAggregateITCase begin to fail.
This patch can be used to reproduce the issue[1].
https://github.com/sjwiesman/flink/tree/keygrouprangecheck
cc [~jincheng] [~hequn8128]
was:
The implementation of flat aggregate appears to misuse key group ranges. When we add a check in AbstractStreamOperator that the current key belongs to the key group assigned to that subtask tests in TableAggregateITCase begin to fail.
This patch can be used to reproduce the issue[1].
https://github.com/sjwiesman/flink/tree/keygrouprangecheck
cc [~jincheng] [~hequn8128]
> Flat aggregate misuses key group ranges
> ---------------------------------------
>
> Key: FLINK-16223
> URL: https://issues.apache.org/jira/browse/FLINK-16223
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.10.0, 1.11.0
> Reporter: Seth Wiesman
> Priority: Major
>
> The implementation of flat aggregate appears to misuse key group ranges. When we add a check in AbstractStreamOperator that the current key belongs to the key group assigned to that subtask, tests in TableAggregateITCase begin to fail.
> This patch can be used to reproduce the issue[1].
> https://github.com/sjwiesman/flink/tree/keygrouprangecheck
> cc [~jincheng] [~hequn8128]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)