[FLINK-14014] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Resolved
• Fix Version/s: 1.10.0
• Component/s: API / Python
• Labels: pull-request-available
• Assignee: Dian Fu
• Reporter: Dian Fu
• Created: 09/Sep/19 13:20
• Updated: 30/Sep/19 13:49
• Resolved: 18/Sep/19 15:14

Description

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:

1. Internally, it uses Apache Beam’s portability for Python UDF execution and this is transparent for the caller of PythonScalarFunctionRunner
2. By default, each runner will startup a separate Python worker
3. The Python worker can run in a docker, a separate process or even an non-managed external service.
4. It has the ability to execute multiple Python ScalarFunctions
5. It also supports chained Python ScalarFunctions

Issue Links

• causes: FLINK-14226 Subset of nightly tests fail due to No output has been received in the last 10m0s
• links to: GitHub Pull Request #9653