WeiZhong94 opened a new pull request #12077:
URL: https://github.com/apache/flink/pull/12077


   ## What is the purpose of the change
   
   *This pull request adds the parse logic of Python command line options to 
CliOptionsParser in SQL Client.*
   
   
   ## Brief change log
   
     - *Add the parse logic of Python command line options to CliOptionsParser 
in SQL Client.*
     - *Append the Python configurations from CliOptions to Session 
Environment.*
   
   ## Verifying this change
   
   This change can be verified as follows:
   
     - *Start a local standalone flink cluster.*
     - *Prepare a sql client session environment file with python UDF 
declaration.*
     - *Added test that validates that TaskInfo is transferred only once across 
recoveries*
     - *Launch the sql client with command line option "-pyfs xxx.py", "xxx.py" 
is the path of the python file that defines the python UDF.*
     - *The sql client should up without any exception.*
   
   **NOTE:** After adding the PyFlink e2e test, the changes in this PR will be 
automatically verified.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - 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, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   


----------------------------------------------------------------
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:
[email protected]


Reply via email to