[
https://issues.apache.org/jira/browse/BEAM-12212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17350095#comment-17350095
]
Beam JIRA Bot commented on BEAM-12212:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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, stale-assigned
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
