You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Rong Rong (JIRA)" <ji...@apache.org> on 2018/05/03 15:48:00 UTC

[jira] [Updated] (FLINK-9294) Improve type inference for UDFs with composite parameter or result type

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

Rong Rong updated FLINK-9294:
-----------------------------
    Description: 
For now 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.

  was:
For now 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 &amp; SQL
>            Reporter: Rong Rong
>            Priority: Major
>
> For now 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)