[
https://issues.apache.org/jira/browse/BEAM-8096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916307#comment-16916307
]
Jack Whelpton commented on BEAM-8096:
-------------------------------------
I suspect the change may be as simple as this:
[https://github.com/jackwhelpton/beam/commit/d1711f43e685c0f41b366437eb28cf5a25c436f0]
would this suffice for a PR? There don't appear to be any obvious tests around
this area that I could build on, but if anybody can point me in the right
direction that'd be great.
> Allow runner to configure "subnetwork"
> --------------------------------------
>
> Key: BEAM-8096
> URL: https://issues.apache.org/jira/browse/BEAM-8096
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Affects Versions: 2.15.0
> Reporter: Jack Whelpton
> Priority: Major
>
> When running a Dataflow job, the network can be specified using the --network
> flag; however, there is no support for doing the same for the subnetwork.
> This would be the go equivalent of the following Java code:
> [https://cloud.google.com/dataflow/java-sdk/JavaDoc/com/google/cloud/dataflow/sdk/options/DataflowPipelineWorkerPoolOptions.html#getSubnetwork--|https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/options/DataflowPipelineWorkerPoolOptions.java#L151]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
