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 2020/10/19 17:10:01 UTC
[jira] [Commented] (BEAM-10773) worker_harness_container_image flag
has no effect
[ https://issues.apache.org/jira/browse/BEAM-10773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216926#comment-17216926 ]
Beam JIRA Bot commented on BEAM-10773:
--------------------------------------
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.
> worker_harness_container_image flag has no effect
> -------------------------------------------------
>
> Key: BEAM-10773
> URL: https://issues.apache.org/jira/browse/BEAM-10773
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Brian M
> Priority: P2
> Labels: stale-P2
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Setting the `worker_harness_container_image` flag to a custom built worker doesn't seem to have any impact when launching on dataflow. The default apache/beam_go_sdk:latest image is always used.
> {code:java}
> $ go run sdks/go/examples/wordcount/wordcount.go --output=gs://.../tmp/out.txt --project=... --runner=dataflow --region=us-central1 --temp_location gs://.../tmp --staging_location gs://.../staging --worker_harness_container_image=fake/image:latest
> 2020/08/19 22:56:28 WARNING: proto: file "v1.proto" is already registered
> 2020/08/19 22:56:28 No environment config specified. Using default config: 'apache/beam_go_sdk:latest'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)