Samrat002 opened a new pull request, #21770:
URL: https://github.com/apache/flink/pull/21770

   
   ## What is the purpose of the change
   
   Currently, below are the ways Python Worker gets the Python Flink 
Dependencies.
   
   1. Worker Node's System Python Path 
(/usr/local/lib64/python3.7/site-packages)
   2. Client passes the python Dependencies through `-pyfs` and `--pyarch` 
which is localised into `PYTHONPATH` of Python Worker.
   3. Client passes the requirements through `-requirement.txt` which gets 
installed on Worker Node and added into `PYTHONPATH` of Python Worker.
   
   This change allow `PYTHONPATH` of Python Worker configurable where 
Admin/Service provider can install the required python Flink dependencies on a 
custom path (`/usr/lib/pyflink/lib/python3.7/site-packages`) on all Worker 
Nodes and then set the path in the client machine configuration 
`flink-conf.yaml`. This way it works without any configurations from the 
Application Users and also without affecting any other components dependent on 
System Python Path.
   
   
   ## Brief change log
   Todo
   
   ## Verifying this change
   Todo
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / no) no 
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / no) no
     - The serializers: (yes / no / don't know) no
     - The runtime per-record code paths (performance sensitive): (yes / no / 
don't know) don't know
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know) 
no 
     - The S3 file system connector: (yes / no / don't know) no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / no) no
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs 
/ not documented) N/A
   


-- 
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.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to