GitHub user lidavidm added a comment to the discussion: CGO dependency as adoption blocker for C++ engines
The C++ implementation hit unsolvable dependency issues, unfortunately. If you ever plan on using Protobuf, gRPC, or possibly arrow-cpp inside your application, it's possible you'll run into the same issues. Could you expand on the latency concern? I'm not sure how the Go runtime would add meaningful latency compared to, say, sending a query across the network to the cloud, waiting for it, and fetching the result. (If you're worried about the Go runtime taking resources from the host, we can explore ways to control that / gRPC-C++ itself effectively has a runtime with its own thread pools, too; and I'm not sure a driver built with either would be actually unloadable/dlclose-able due to global state.) GitHub link: https://github.com/apache/arrow-adbc/discussions/4156#discussioncomment-16379590 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
