[GitHub] [arrow-adbc] lidavidm commented on issue #887: python/adbc_driver_flightsql: Connection management and per request headers

["lidavidm (via GitHub)" <gi...@apache.org>]

lidavidm commented on issue #887:
URL: https://github.com/apache/arrow-adbc/issues/887#issuecomment-1626043111

   While Flight SQL is *mostly* stateless (note that some contributors are attempting to change this!) it's still best to reuse connections where possible, both because there is state we are requesting from the server, and because that lets gRPC maintain a single TCP connection instead of having to constantly set up and tear down more.
   
   For Flight SQL specifically, the connection should be thread safe, but ADBC does not guarantee this (so connection-per-worker or a pool is better).
   
   You can set the header on the statement; this won't affect other connections (and will go away when you close the statement). Statements are fairly cheap (it's just a bit of state tracking the query string etc.)


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org