You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Robert Bradshaw (Jira)" <ji...@apache.org> on 2022/05/05 16:18:00 UTC

[jira] [Updated] (BEAM-14421) --dataflowServiceOptions=use_runner_v2 is broken

     [ https://issues.apache.org/jira/browse/BEAM-14421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Bradshaw updated BEAM-14421:
-----------------------------------
    Description: Per [https://lists.apache.org/list.html?user@beam.apache.org] passing `–dataflowServiceOptions=use_runner_v2` alone triggers pipeline errors. This is surprising as it should be an alias for experiments, and furthermore no action should be required on the SDK side to produce a runner v2 compatible graph.  (was: Per [https://lists.apache.org/list.html?user@beam.apache.org] passing `–dataflowServiceOptions=use_runner_v2` alone triggers pipeline errors.)

> --dataflowServiceOptions=use_runner_v2 is broken
> ------------------------------------------------
>
>                 Key: BEAM-14421
>                 URL: https://issues.apache.org/jira/browse/BEAM-14421
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow, sdk-java-core
>    Affects Versions: 2.38.0
>            Reporter: Robert Bradshaw
>            Priority: P1
>
> Per [https://lists.apache.org/list.html?user@beam.apache.org] passing `–dataflowServiceOptions=use_runner_v2` alone triggers pipeline errors. This is surprising as it should be an alias for experiments, and furthermore no action should be required on the SDK side to produce a runner v2 compatible graph.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)