[
https://issues.apache.org/jira/browse/FLINK-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180630#comment-16180630
]
Timo Walther commented on FLINK-7678:
-------------------------------------
[~walterddr] I looked into your issue. The functions that you implemented are
not correct. {{CompositeType}} is type information and row an instance that
type information describes. In your case you can simply use {{eval(row: Row)}}
or {{eval(row: (String, Int))}} (depending on your type). I added additional
tests to test the behavior, you can also use them as examples:
https://github.com/apache/flink/pull/4726
> SQL UserDefineTableFunction does not take CompositeType input correctly
> -----------------------------------------------------------------------
>
> Key: FLINK-7678
> URL: https://issues.apache.org/jira/browse/FLINK-7678
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 1.3.2
> Reporter: Rong Rong
> Assignee: Timo Walther
>
> UDF is using FlinkTypeFactory to infer operand type while UDTF does not go
> through the same code path. This result in:
> {code:console}
> org.apache.flink.table.api.ValidationException: SQL validation failed. From
> line 1, column 38 to line 1, column 44: No match found for function signature
> func(<COMPOSITE(Row(f0: Integer, f1: String))>)
> Caused by: org.apache.calcite.runtime.CalciteContextException: From line 1,
> column 38 to line 1, column 44: No match found for function signature
> func(<COMPOSITE(Row(f0: Integer, f1: String))>)
> {code}
> Please see github code for more info:
> https://github.com/walterddr/flink/blob/bug_report/flink-libraries/flink-table/src/test/scala/org/apache/flink/table/api/batch/sql/UDTFCompositeTypeTestFailure.scala
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
