zeroshade commented on issue #48: URL: https://github.com/apache/arrow-go/issues/48#issuecomment-4683528015
Closing as stale / known limitation. This report references the retired monorepo packages `github.com/apache/arrow/go/v12` and `.../v13`. Arrow Go has since moved to the standalone `github.com/apache/arrow-go` module. The root cause is the documented protobuf global-registry behavior (https://protobuf.dev/reference/go/faq#namespace-conflict): the generated `Flight.proto` descriptor registers under a fixed global name, so importing two major versions that both register it will always panic. This is inherent to `protoc-gen-go` global registration and is not specific to Arrow. The only real fix would be to extract the generated Flight protobuf code into its own separately-versioned module shared across Arrow versions — an invasive change to the module layout and release process that we are not planning to pursue. In practice, projects should depend on a single major version of the Flight bindings. If consolidating the generated proto into a shared module becomes worthwhile, it can be tracked as a dedicated proposal. -- 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]
