You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Joe Moser (Jira)" <ji...@apache.org> on 2021/08/18 09:47:00 UTC
[jira] [Commented] (FLINK-22913) Support Python UDF chaining in
Python DataStream API
[ https://issues.apache.org/jira/browse/FLINK-22913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400947#comment-17400947 ]
Joe Moser commented on FLINK-22913:
-----------------------------------
[~dian.fu] do you think Separate data and timer connection into different channels for Python Table API operators will make it to 1.14 or should we update the fixVersion and move it into a new parent ticket?
> Support Python UDF chaining in Python DataStream API
> ----------------------------------------------------
>
> Key: FLINK-22913
> URL: https://issues.apache.org/jira/browse/FLINK-22913
> Project: Flink
> Issue Type: Improvement
> Components: API / Python
> Reporter: Dian Fu
> Assignee: Dian Fu
> Priority: Major
> Fix For: 1.14.0
>
>
> Currently, for the following job:
> {code}
> ds = ..
> ds.map(map_func1)
> .map(map_func2)
> {code}
> The Python function `map_func1` and `map_func2` will runs in separate Python workers and the result of `map_func1` will be transferred to JVM and then transferred to `map_func2` which may resides in another Python worker. This introduces redundant communication and serialization/deserialization overhead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)