You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Brian M (Jira)" <ji...@apache.org> on 2020/08/20 03:11:00 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=17180938#comment-17180938 ]
Brian M commented on BEAM-10773:
--------------------------------
Looking at sdks/go/pkg/beam/runners/dataflow/dataflow.go I can see that this flag is set to the `image` variable, but AFAICT that variable is never consumed for anything.
Based on this history, the changes in [https://github.com/apache/beam/commit/5f46b678e001d55621e5de719cf782160b1ba67d#diff-baacafffaacf38819d0a42b9d41d3174L228] look relevant.
> 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
>
> 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)