aiguofer opened a new issue, #887: URL: https://github.com/apache/arrow-adbc/issues/887
For applications that make requests to a FlightSql server, how should connections be handled? My initial assumption was that since there is no state associated with the connection and it's simply making gRPC requests, that I could just create a connection on each request. However, I'm noticing this adds ~100ms latency per request. Although it's not the end of the world, this seems a little excessive. Digging into it a little, I noticed that when I establish a connection it makes a `getFlightInfoSqlInfo` request (oddly enough, it doesn't also make the `getStreamSqlInfo` request). This left me with a few questions: - Should we maintain long lived connections? - What kind of state or socket connection is associated with a connection? - If so, is a single connection thread safe, or should we have a connection per worker thread (or some sort of pool to manage this)? - If we're maintaining a long lived connection and we want to pass a specific header when we execute a query, is there a way to pass a specific header only for that query? -- 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]
