[
https://issues.apache.org/jira/browse/FLINK-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598895#comment-16598895
]
Rong Rong commented on FLINK-9501:
----------------------------------
https://github.com/apache/flink/pull/6472 introduced some of the generic type
inference functionalities by relaxing the search in FunctionCatalog lookup.
Thus the purpose of this JIRA has changed. it should enforce additional
validations instead.
> Allow Object or Wildcard type in user-define functions as parameter types but
> not result types
> ----------------------------------------------------------------------------------------------
>
> Key: FLINK-9501
> URL: https://issues.apache.org/jira/browse/FLINK-9501
> Project: Flink
> Issue Type: Sub-task
> Components: Table API & SQL
> Reporter: Rong Rong
> Assignee: Rong Rong
> Priority: Major
>
> Idea here is to treat every Java parameter objects type as SQL ANY type.
> While disallowing SQL ANY type in result object.
> This ticket is specifically to deal with composite types (with nested schema
> or sub schema) such as generic erasure types
> {code:java}
> public String eval(Map<String, ?> mapArg) { /* ... */ }
> public String eval(Map<String, Object> mapArg) { /* ... */ }
> public String eval(Row rowArg) { /* ... */ }
> {code}
> Update 08/2018
> With FLINK-9294 covering some of the generic type erasure. The additional
> changes needed are:
> 1. Modify FunctionCatalog lookup to use SQL ANY type when a higher level type
> matching is not viable.
> 2. Introduce additional FunctionCatalog lookup checks to ensure that
> additional informations provided by type inference is used for validation
> purpose.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
