[GitHub] [flink] dianfu opened a new pull request #9653: [FLINK-14014][python] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution

[GitBox <gi...@apache.org>]

dianfu opened a new pull request #9653: [FLINK-14014][python] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution
URL: https://github.com/apache/flink/pull/9653
 
 
   
   ## What is the purpose of the change
   
   *This pull request introduces PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution. Internally, it uses Apache Beam's portability framework for Python UDF execution.*
   
   ## Brief change log
   
     - *It bumps maven-shade-plugin to 3.1.0 as version below 3.1.0 could not work well with ASM 6.0([MSHADE-258](https://issues.apache.org/jira/browse/MSHADE-258)) which is dependent by Beam*
     - *It introduces basic classes such as PythonEnv, PythonFunction, PythonFunctionInfo into flink-table-common which hold the information such as the Python execution environment, the serialized Python functions, etc. These classes are located in flink-table-common because they will be used by the added RelNode which will be introduced later*
     - *Introduces a series of PythonFunctionRunners. They are responsible for using Beam's portability framework for Python UDF execution*
     - *Handle the license statements as it introduces a few third-part dependences are introduced because of we depends on Beam*
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *The added PythonScalarFunctionRunnerTest, BeamTypeUtilsTest*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes)
     - If yes, how is the feature documented? (JavaDocs)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services