lidavidm commented on issue #34612: URL: https://github.com/apache/arrow/issues/34612#issuecomment-1474359548
We intentionally separate Flight from gRPC. Other Flight implementations can use alternative transports, so exposing gRPC directly from the core API is not desirable. You wouldn't need all the logic in Builder.build. You would be able to customize the channel as desired. Exposing/wrapping all of the different gRPC builder options and ensuring they work with Flight is a lot of work. That is why we offer this escape hatch in the first place. It may make sense to expose toSocketAddress. -- 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]
