You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/02/06 17:15:02 UTC
[jira] [Commented] (BEAM-11414) Make expansion service Java
launcher configurable in pipeline options.
[ https://issues.apache.org/jira/browse/BEAM-11414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280239#comment-17280239 ]
Beam JIRA Bot commented on BEAM-11414:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Make expansion service Java launcher configurable in pipeline options.
> ----------------------------------------------------------------------
>
> Key: BEAM-11414
> URL: https://issues.apache.org/jira/browse/BEAM-11414
> Project: Beam
> Issue Type: New Feature
> Components: sdk-py-core
> Reporter: Kyle Weaver
> Priority: P2
> Labels: stale-P2
>
> We need Java to run expansion services in subprocesses [1]. Currently this code always uses the "java" executable on the $PATH. But changing $PATH or adding an alias is a global(ish) change, and it's cumbersome, or even impossible in some environments (Forge). Having a pipeline option for it is easier and better isolated.
> [1] https://github.com/apache/beam/blob/master/sdks/python/apache_beam/utils/subprocess_server.py
--
This message was sent by Atlassian Jira
(v8.3.4#803005)