Repository navigation
[C++][FlightRPC][ODBC] Driver fails when an endpoint location is arrow-flight-reuse-connection://? #54649
Description
Describe the bug, including details regarding any error messages, version, and platform.
When a Flight SQL server returns arrow-flight-reuse-connection://? as the location of a FlightEndpoint, the ODBC driver fails with:
No client transport implementation for arrow-flight-reuse-connection
FlightStreamChunkBuffer only calls DoGet on the existing client when the location list is empty. For any other location it calls FlightClient::Connect(endpoint_locations[0], ...), and no transport is registered for the reuse-connection scheme:
GH-40345 (#40084) defined this location as "fetch on the current connection" and added support for it in C++, Java and Go, and the JDBC driver handles it in ArrowFlightSqlClientHandler. The ODBC driver came later and doesn't check for it. GetInfo reads through the same buffer, so the DSN dialog's Test Connection fails too.
We hit this with a pyarrow-based Flight SQL proxy that rewrites endpoints to the reuse-connection location, using the ODBC driver built from 24.0.0 on Windows. A fix that treats the location like an empty list, plus a test in flight_sql_stream_chunk_buffer_test.cc, is ready, and I can open a PR.
Component(s)
C++, FlightRPC
Activity