[
https://issues.apache.org/jira/browse/FLINK-10259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619867#comment-16619867
]
Fabian Hueske edited comment on FLINK-10259 at 9/19/18 8:00 PM:
----------------------------------------------------------------
Fixed for 1.5.5 with 5852a25d8d9a4defa70c31ae61231471dc484bc1
Fixed for 1.6.2 with 290d96e50f864468b6b2d2a3b741e0fbdaee5df0
Fixed for 1.7.0 with f28b82909c3c6bcbe0436cae41af9a3c001f1c36
was (Author: fhueske):
Fixed for 1.5.5 with 5852a25d8d9a4defa70c31ae61231471dc484bc1
Fixed for 1.6.2 with 1ee6bc3b99d8f50fb8ed0be0b4936c83ce03fff1
Fixed for 1.7.0 with f28b82909c3c6bcbe0436cae41af9a3c001f1c36
> Key validation for GroupWindowAggregate is broken
> -------------------------------------------------
>
> Key: FLINK-10259
> URL: https://issues.apache.org/jira/browse/FLINK-10259
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Reporter: Fabian Hueske
> Assignee: Fabian Hueske
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0, 1.6.2, 1.5.5
>
>
> WindowGroups have multiple equivalent keys (start, end) that should be
> handled differently from other keys. The {{UpdatingPlanChecker}} uses
> equivalence groups to identify equivalent keys but the keys of WindowGroups
> are not correctly assigned to groups.
> This means that we cannot correctly extract keys from queries that use group
> windows.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
