[ https://issues.apache.org/jira/browse/FLINK-22781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370983#comment-17370983 ]
Jingsong Lee commented on FLINK-22781: -------------------------------------- Although it is an Experimental API, we already exposed it through user mail list and other channels. So I think it is better to start a discussion on the mail list and finally make one really Public. > Incorrect result for group window aggregate when mini-batch is enabled > ---------------------------------------------------------------------- > > Key: FLINK-22781 > URL: https://issues.apache.org/jira/browse/FLINK-22781 > Project: Flink > Issue Type: Bug > Components: Table SQL / Planner > Affects Versions: 1.14.0 > Reporter: godfrey he > Assignee: JING ZHANG > Priority: Critical > Labels: pull-request-available > Fix For: 1.14.0 > > > We can reproduce this issue through adding the following code to > {{GroupWindowITCase#testWindowAggregateOnUpsertSource}} method: > {code:java} > tEnv.getConfig.getConfiguration.setBoolean( > ExecutionConfigOptions.TABLE_EXEC_MINIBATCH_ENABLED, true) > tEnv.getConfig.getConfiguration.set( > ExecutionConfigOptions.TABLE_EXEC_MINIBATCH_ALLOW_LATENCY, > Duration.ofSeconds(1)) > tEnv.getConfig.getConfiguration.setLong( > ExecutionConfigOptions.TABLE_EXEC_MINIBATCH_SIZE, 10L) > {code} > The reason is the group window without any data (the data may be retracted) > should not send any record. -- This message was sent by Atlassian Jira (v8.3.4#803005)