Hi Weizhong, Thanks for proposing this feature. In geneal, I'm +1 from the table's view.
I have one suggestion: I think the register python function into catalog doesn't need to startup python process (the "High Level Sequence Diagram" in your FLIP). Because only meta-information is persisted into catalog, we don't need to store "return type", "input types" into catalog. I guess the python process is required when compiling a SQL job. Best, Jark On Fri, 28 Feb 2020 at 19:04, Benchao Li <[email protected]> wrote: > Big +1 for this feature. > > We built our SQL platform on Java Table API, and most common UDF are > implemented in Java. However some python developers are not familiar with > Java/Scala, and it's very inconvenient for these users to use UDF in SQL. > > Wei Zhong <[email protected]> 于2020年2月28日周五 下午6:58写道： > >> Thank for your reply Dan! >> >> By the way, this FLIP is closely related to the SQL API. @Jark Wu < >> [email protected]> @Timo <[email protected]> could you please take a >> look? >> >> Thanks, >> Wei >> >> > 在 2020年2月25日，16:25，zoudan <[email protected]> 写道： >> > >> > +1 for supporting Python UDF in Java/Scala Table API. >> > This is a great feature and would be helpful for python users! >> > >> > Best, >> > Dan Zou >> > >> > >> >> > > -- > > Benchao Li > School of Electronics Engineering and Computer Science, Peking University > Tel:+86-15650713730 > Email: [email protected]; [email protected] > >
