benbellick commented on PR #1399: URL: https://github.com/apache/arrow-go/pull/1399#issuecomment-6960549715
@zeroshade This actually isn't about binary size. We have a large monorepo that depends on `substrait-go`, `arrow-go`, and `iceberg-go`, and we want to upgrade our Substrait version at a faster cadence. These protobuf updates often include breaking changes to the generated Go API, so we can't simply override the transitive dependency in our monorepo. We need the libraries using it to be updated as well. That can mean: 1. Bump `substrait-protobuf` in `substrait-go`, make any necessary compatibility changes, and cut a release. 2. Update `substrait-go` in `arrow-go`, make any necessary compatibility changes, and cut a release. 3. Update `arrow-go` in `iceberg-go`, make any necessary compatibility changes, and cut a release. 4. Update those dependencies together in our monorepo. We can't use different versions of the protobuf-dependent libraries side by side, because their generated definitions would conflict in [protobuf's global registry](https://protobuf.dev/reference/go/faq/#namespace-conflict). With `substrait-go/v9`, Arrow no longer depends on the generated protobuf code. Our code could then use `substrait-go/v10` while Arrow and Iceberg stay on `substrait-go/v9`, since we don't pass expressions between our code and their integration. E.g. this is why I updated [`arrow-go` here](https://github.com/apache/arrow-go/pull/754), followed by [`iceberg-go` here](https://github.com/apache/iceberg-go/pull/949). -- 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]
