[jira] [Updated] (FLINK-21222) Support loopback mode to allow Python UDF worker and client reuse the same Python VM

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-21222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-21222:
-----------------------------------
    Labels: stale-assigned  (was: )

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issue is assigned but has not received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a comment updating the community on your progress.  If this issue is waiting on feedback, please consider this a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone else may work on it. If the "warning_label" label is not removed in 7 days, the issue will be automatically unassigned.


> Support loopback mode to allow Python UDF worker and client reuse the same Python VM
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-21222
>                 URL: https://issues.apache.org/jira/browse/FLINK-21222
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Python
>            Reporter: Dian Fu
>            Assignee: Dian Fu
>            Priority: Major
>              Labels: stale-assigned
>
> Currently the Python process for the client and the Python UDF worker runs in different Python processes. It would bring the following benefits if we could support loopback mode to allow Python UDF worker and client reuse the same Python VM:
> 1) It could greatly reduce the job initialization overhead in mini-cluster mode as there is no need to start the Python process any more.
> 2) It makes the debug easier.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)