You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2017/11/15 16:44:00 UTC
[jira] [Updated] (FLINK-7678) SQL UserDefineTableFunction does not
take CompositeType input correctly
[ https://issues.apache.org/jira/browse/FLINK-7678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther updated FLINK-7678:
--------------------------------
Fix Version/s: 1.5.0
1.4.0
> 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
> Fix For: 1.4.0, 1.5.0
>
>
> 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)