lidavidm commented on issue #43819: URL: https://github.com/apache/arrow/issues/43819#issuecomment-2316453579
My thought at least is that you would interact with Arrow streams only via byte payloads - so basically your contract is simply "provide the payloads in order to the Flight reader/writer". I don't think there's any appetite to expose those workings to you except that you will have to ferry them from gRPC to the reader now. (If anything, Flight itself gets firewalled from those details - we have to duplicate code in arrow::ipc because it's not exposed to us even.) -- 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]
