You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Prabhu Joseph (Jira)" <ji...@apache.org> on 2022/12/02 11:02:00 UTC
[jira] [Updated] (FLINK-30277) Allow PYTHONPATH of Python Worker configurable
[ https://issues.apache.org/jira/browse/FLINK-30277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prabhu Joseph updated FLINK-30277:
----------------------------------
Summary: Allow PYTHONPATH of Python Worker configurable (was: Allow PYTHONPATH of Python Worker to be configurable)
> Allow PYTHONPATH of Python Worker configurable
> ----------------------------------------------
>
> Key: FLINK-30277
> URL: https://issues.apache.org/jira/browse/FLINK-30277
> Project: Flink
> Issue Type: Improvement
> Components: API / Python
> Affects Versions: 1.16.0
> Reporter: Prabhu Joseph
> Priority: Major
>
> Currently, below are the ways Python Worker gets the Python Flink Dependencies.
> # Worker Node's System Python Path (/usr/local/lib64/python3.7/site-packages)
> # Client passes the python Dependencies through -pyfs and --pyarch which is localized into PYTHONPATH of Python Worker.
> # Client passes the requirements through -pyreq which gets installed on Worker Node and added into PYTHONPATH of Python Worker.
> This Jira intends to allow PYTHONPATH of Python Worker to be configurable where admin/Service provider can install the required python flink depencies 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.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)