[
https://issues.apache.org/jira/browse/FLINK-9294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rong Rong updated FLINK-9294:
-----------------------------
Description:
Most of the UDF function signatures that includes composite types such as
*{{MAP}}*, *{{ARRAY}}*, etc would require user to override
*{{getParameterType}}* or *{{getResultType}}* method explicitly.
It should be able to resolve the composite type based on the function
signature, such as:
{code:java}
public List<String> eval(Map<String, Integer> mapArg) {
//...
}
{code}
should automatically resolve *{{ObjectArrayTypeInfo<BasicTypeInfo.STRING>}}* &
*{{MapTypeInfo<BasicTypeInfo.STRING, BasicTypeInfo.INTEGER>}}* to be the result
type and parameter type.
was:
Most of the UDF function signatures that includes composite types such as
*{{MAP}}*, *{{ARRAY}}*, etc would require user to override
*{{getParameterType}}* or *{{getResultType}}* method explicitly.
It should be able to resolve the composite type based on the function signature.
> Improve type inference for UDFs with composite parameter or result type
> ------------------------------------------------------------------------
>
> Key: FLINK-9294
> URL: https://issues.apache.org/jira/browse/FLINK-9294
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Rong Rong
> Assignee: Rong Rong
> Priority: Major
>
> Most of the UDF function signatures that includes composite types such as
> *{{MAP}}*, *{{ARRAY}}*, etc would require user to override
> *{{getParameterType}}* or *{{getResultType}}* method explicitly.
> It should be able to resolve the composite type based on the function
> signature, such as:
> {code:java}
> public List<String> eval(Map<String, Integer> mapArg) {
> //...
> }
> {code}
> should automatically resolve *{{ObjectArrayTypeInfo<BasicTypeInfo.STRING>}}*
> & *{{MapTypeInfo<BasicTypeInfo.STRING, BasicTypeInfo.INTEGER>}}* to be the
> result type and parameter type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
