[ 
https://issues.apache.org/jira/browse/BEAM-13939?focusedWorklogId=749691&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-749691
 ]

ASF GitHub Bot logged work on BEAM-13939:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Mar/22 22:50
            Start Date: 29/Mar/22 22:50
    Worklog Time Spent: 10m 
      Work Description: lostluck commented on pull request #16961:
URL: https://github.com/apache/beam/pull/16961#issuecomment-1082444862


   Tiny note: https://github.com/apache/beam/pull/17045 is ready to go in, and 
it makes a necessary change to graphx/v1.proto. If there are weird merge 
conflicts, it should be fine if you just re-generate.
   
   I also have a small change I need to make to that same file to fix a 
different bug, which would also need regeneration.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 749691)
    Time Spent: 22h 50m  (was: 22h 40m)

> Go SDK: Protobuf namespace conflict
> -----------------------------------
>
>                 Key: BEAM-13939
>                 URL: https://issues.apache.org/jira/browse/BEAM-13939
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model, sdk-go
>    Affects Versions: 2.36.0
>            Reporter: Milan Patel
>            Priority: P2
>         Attachments: demobug.zip
>
>          Time Spent: 22h 50m
>  Remaining Estimate: 0h
>
> The Go SDK generated grpc protobufs are not namespaced with enough 
> granularity. If a user has another external dependency with the same protobuf 
> file registered with the proto runtime, their compiled binary will panic at 
> runtime pointing the user to this [doc 
> page|https://developers.google.com/protocol-buffers/docs/reference/go/faq#fix-namespace-conflict].
>  
> In the interim, following the instructions to add either ldflags to the 
> compiler or an environment var to the binary works, but this is an unideal 
> solution since only one of the duplicate proto specifications will be 
> accessible from a [global 
> registry|https://pkg.go.dev/google.golang.org/[email protected]/reflect/protoregistry].
>  
> Ask: Regenerate the go protos such that descriptors like 
> [these|https://github.com/apache/beam/blob/84353a7c973d3acaaa56d81c265dce7193a56be5/sdks/go/pkg/beam/model/pipeline_v1/metrics.pb.go#L797-L811]
>  are outputted with filenames that are more granular, such as a filename that 
> includes the directory structure of the repository.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to