[ 
https://issues.apache.org/jira/browse/FLINK-14013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950731#comment-16950731
 ] 

Dian Fu edited comment on FLINK-14013 at 10/14/19 5:57 AM:
-----------------------------------------------------------

[~sunjincheng121] Thanks a lot. It makes sense to me as there may be some 
features missing in 1.10. I will set the "Fix version" for the features which 
are not planned to support in 1.10 as "None" for now as tag 1.11 is still not 
created. What do you think?


was (Author: dian.fu):
[~sunjincheng121] Thanks a lot. It makes sense to me as there may be some 
features missing in 1.10. I will set the features which are not planned to 
support in 1.10 as "None" for now as tag 1.11 is still not created. What do you 
think?

> Support Flink Python User-Defined Stateless Function for Table
> --------------------------------------------------------------
>
>                 Key: FLINK-14013
>                 URL: https://issues.apache.org/jira/browse/FLINK-14013
>             Project: Flink
>          Issue Type: New Feature
>          Components: API / Python, Table SQL / API
>    Affects Versions: 1.10.0
>            Reporter: Dian Fu
>            Priority: Major
>
> The Python Table API has been supported in release 1.9.0. See the 
> [FLIP-38|https://cwiki.apache.org/confluence/display/FLINK/FLIP-38%3A+Python+Table+API]
>  and FLINK-12308 for details. However, currently Python user-defined 
> functions are still not supported. In this FLIP, we want to support stateless 
> Python user-defined functions in Python Table API.
> More detailed description could be found in 
> [FLIP-58|https://cwiki.apache.org/confluence/display/FLINK/FLIP-58%3A+Flink+Python+User-Defined+Stateless+Function+for+Table].
> The discussion could be found in [mailing 
> thread|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Flink-Python-User-Defined-Function-for-Table-API-td31673.html].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to