[jira] [Resolved] (FLINK-8013) Check of AggregateFunction merge function signature is too strict.

["Timo Walther (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther resolved FLINK-8013.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.0
                   1.4.0

Fixed in 1.5: 11218a35dc0fdd7439142a313e6628c51cffe689
Fixed in 1.4: 32bfc38875faa5baea0dc63d91e1273d7df7b2ef

> Check of AggregateFunction merge function signature is too strict.
> ------------------------------------------------------------------
>
>                 Key: FLINK-8013
>                 URL: https://issues.apache.org/jira/browse/FLINK-8013
>             Project: Flink
>          Issue Type: Bug
>          Components: Table API & SQL
>    Affects Versions: 1.4.0
>            Reporter: Fabian Hueske
>            Assignee: Timo Walther
>             Fix For: 1.4.0, 1.5.0
>
>
> The {{AggregationCodeGenerator}} checks that a user-defined {{AggregateFunction}} implements all required methods. However, the check for the {{merge(accumulator: ACC, its: java.lang.Iterable\[ACC\]): Unit}} method is too strict and rejects valid UDAGGs. 
> This happens for more complex accumulators such as {{Array\[org.apache.flink.api.java.tuple.Tuple2\[java.lang.Integer, java.lang.Float\]\]}} because generic types are lost such that the check of the argument types of {{merge}} fails.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)