You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Emily Ye (Jira)" <ji...@apache.org> on 2021/04/22 19:16:00 UTC

[jira] [Commented] (BEAM-12212) Add sdkContainerImage flag to (eventually) replace workerHarnessContainerImage

    [ https://issues.apache.org/jira/browse/BEAM-12212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329366#comment-17329366 ] 

Emily Ye commented on BEAM-12212:
---------------------------------

Note that this new flag should be the flag for custom containers going forward.  

> Add sdkContainerImage flag to (eventually) replace workerHarnessContainerImage
> ------------------------------------------------------------------------------
>
>                 Key: BEAM-12212
>                 URL: https://issues.apache.org/jira/browse/BEAM-12212
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-harness, sdk-py-harness
>            Reporter: Emily Ye
>            Assignee: Emily Ye
>            Priority: P2
>              Labels: containers
>
> workerHarnessContainerImage (dataflow-only) is a legacy flag from a time where Dataflow packaged the worker and SDK together in on container. As we move towards portable world where remote runners will generally have a containerized SDK process, we wanted a new flag  that can be reused across runners. 
> We want it to reflect that it's only the SDK and remove harness from the name, since "harness" is meaningless to most users ("what are we harnessing?").



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