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

Timo Walther closed FLINK-26518.
--------------------------------
    Fix Version/s: 1.15.0
     Release Note: Table functions that are called using Scala implicit 
conversions have been updated to use the new type system and new type 
inference. Users are requested to update their UDFs or use the deprecated 
`TableEnvironment.registerFunction` to restore the old behavior temporarily by 
calling the function via name.
       Resolution: Fixed

Fixed in master:

commit e42202be9f80d49eb70a24125ed3269ab9fb1110
[table] Support BridgingSqlFunction with SqlTableFunction for Scala implicits

commit f8cb19e70ca7da6423dfb01b97e05c4d520c9fde
[table-planner] Port FlinkRelBuilder to Java


Fixed in 1.15:

commit aea176e1fc15a9cf0388e8b32ce3bb3688e876bf
[table] Support BridgingSqlFunction with SqlTableFunction for Scala implicits

commit 1e1b182e702ec25a38c3c02d585734415eae110a
[table-planner] Port FlinkRelBuilder to Java

> Support the new type inference in Scala Table API table functions
> -----------------------------------------------------------------
>
>                 Key: FLINK-26518
>                 URL: https://issues.apache.org/jira/browse/FLINK-26518
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> Currently, we cannot distinguish between old and new type inference for Scala 
> Table API because those functions are not registered in a catalog but are 
> used "inline". We should support them as well.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to