[jira] [Commented] (BEAM-11200) Update Go SDK version with release scripts

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-11200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17260672#comment-17260672 ] 

Beam JIRA Bot commented on BEAM-11200:
--------------------------------------

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.

> Update Go SDK version with release scripts
> ------------------------------------------
>
>                 Key: BEAM-11200
>                 URL: https://issues.apache.org/jira/browse/BEAM-11200
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow, sdk-go
>            Reporter: Robert Burke
>            Assignee: Robert Burke
>            Priority: P2
>              Labels: stale-assigned
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Currently the Go SDK is notionally "unversioned" due to it's experimental state, however, a recent push in Dataflow has blocked all SDKs older than 2.21.0 from running against runner v2.
> The Go SDK has been using runner v2 since May 28th (or around the 2.21 tagging, so first really included in 2.22) [https://github.com/apache/beam/pull/11207]
> Jobs not using runner v2 should not be affected.
> The work around for now is to update [https://github.com/apache/beam/blob/master/sdks/go/pkg/beam/runners/dataflow/dataflowlib/job.go#L128] to a version beyond "2.21.0" (say "2.26.0-dev")
>  
> I'm going to update that at head to stop the problem and update the release scripts to automatically increment that version, just like we do for python.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)