You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 18:00:02 UTC

[jira] [Updated] (BEAM-10874) Support both Go versions of proto (v1 & v2) with proto coder.

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

Kenneth Knowles updated BEAM-10874:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Support both Go versions of proto (v1 & v2) with proto coder.
> -------------------------------------------------------------
>
>                 Key: BEAM-10874
>                 URL: https://issues.apache.org/jira/browse/BEAM-10874
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-go
>            Reporter: Robert Burke
>            Assignee: Robert Burke
>            Priority: P3
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Go recently changed how their protocol buffers are generated and introduced a new base interface (protoreflect.Message) as the defacto version of proto.Message.
>  
> But this introduces incompatibilities since they are distinct interfaces.
>  
> The solution is quick: register coders for both protoV1 and protoV2 message interfaces which should sort out the problem.



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