[
https://issues.apache.org/jira/browse/FLINK-14014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932543#comment-16932543
]
Hequn Cheng commented on FLINK-14014:
-------------------------------------
Resolved in master:
e7216eebc846a69272c21375af0f4db8009c2e3e
10cb5abb7d752aeee6e045636446c00e0eda4f00
cc3a27b6a3625c9e89b9e6310ddd55d8c2c5be04
> Introduce PythonScalarFunctionRunner to handle the communication with Python
> worker for Python ScalarFunction execution
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-14014
> URL: https://issues.apache.org/jira/browse/FLINK-14014
> Project: Flink
> Issue Type: Sub-task
> Components: API / Python
> Reporter: Dian Fu
> Assignee: Dian Fu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> PythonScalarFunctionRunner is responsible for Python ScalarFunction execution
> and it only handles the Python ScalarFunction execution and nothing else. So
> its logic should be very simple, forwarding an input element to Python worker
> and fetching the execution results back:
> # Internally, it uses Apache Beam’s portability for Python UDF execution and
> this is transparent for the caller of PythonScalarFunctionRunner
> # By default, each runner will startup a separate Python worker
> # The Python worker can run in a docker, a separate process or even an
> non-managed external service.
> # It has the ability to execute multiple Python ScalarFunctions
> # It also supports chained Python ScalarFunctions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
