[
https://issues.apache.org/jira/browse/BEAM-12212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390701#comment-17390701
]
Beam JIRA Bot commented on BEAM-12212:
--------------------------------------
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.
> 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
> Priority: P2
> Labels: containers, stale-P2
> 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)
