You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Daniel Oliveira (JIRA)" <ji...@apache.org> on 2019/08/16 23:45:00 UTC
[jira] [Work started] (BEAM-7970) Regenerate Go SDK proto files in
correct version
[ https://issues.apache.org/jira/browse/BEAM-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on BEAM-7970 started by Daniel Oliveira.
---------------------------------------------
> Regenerate Go SDK proto files in correct version
> ------------------------------------------------
>
> Key: BEAM-7970
> URL: https://issues.apache.org/jira/browse/BEAM-7970
> Project: Beam
> Issue Type: Bug
> Components: sdk-go
> Reporter: Daniel Oliveira
> Assignee: Daniel Oliveira
> Priority: Major
>
> Generated proto files in the Go SDK currently include this bit:
> {{// This is a compile-time assertion to ensure that this generated file}}
> {{// is compatible with the proto package it is being compiled against.}}
> {{// A compilation error at this line likely means your copy of the}}
> {{// proto package needs to be updated.}}
> {{const _ = proto.ProtoPackageIsVersion2 // please upgrade the proto package}}
>
> This indicates that the protos are being generated as proto v2 for whatever reason. Most likely, as mentioned by this post with someone with a similar issue, because the proto generation binary needs to be rebuilt before generating the files again: [https://github.com/golang/protobuf/issues/449#issuecomment-340884839]
> This hasn't caused any errors so far, but might eventually cause errors if we hit version differences between the v2 and v3 protos.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)