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 2022/01/11 16:58:03 UTC
[jira] [Commented] (BEAM-13024) [Go SDK] Export flags to PipelineOptions on non-dataflow runners.
[ https://issues.apache.org/jira/browse/BEAM-13024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472911#comment-17472911 ]
Beam JIRA Bot commented on BEAM-13024:
--------------------------------------
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.
> [Go SDK] Export flags to PipelineOptions on non-dataflow runners.
> -----------------------------------------------------------------
>
> Key: BEAM-13024
> URL: https://issues.apache.org/jira/browse/BEAM-13024
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Robert Burke
> Assignee: Robert Burke
> Priority: P2
> Labels: stale-assigned
>
> Recently the Go SDK dataflow runner code began adding explicitly set flags to the pipeline options. This made them available to worker code at execution time, if queried with `beam.PipelineOptions.Get`.
> The proposal is to generalize this code and make use of it in all runners (including the direct runner). This would make PipelineOptions a useful concept in the Go SDK.
> Flag filtering and adding here:
> [https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/runners/dataflow/dataflow.go#L281]
> Once implemented for all runners, it should be possible to test use of this in the integration tests to ensure continued function.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)