jduo opened a new issue, #46584: URL: https://github.com/apache/arrow/issues/46584
### Describe the bug, including details regarding any error messages, version, and platform. The current implementation of the ODBC driver does not correctly establish connections to other nodes when a flight result set is distributed. https://github.com/apache/arrow/blob/218c8861f52444dcf7b6d78e1dd266706e584ffe/cpp/src/arrow/flight/sql/odbc/flight_sql/flight_sql_stream_chunk_buffer.cc#L35 At this line, it just calls DoGet() with the ticket at the originating endpoint. It doesn't check the list of locations to see if it is empty (which indicates that this is OK). The correct behavior is to call DoGet() on the current client only if the list of locations in the FlightEndpoint is empty. If it is non-empty, the driver should create a FlightSqlClient to connect to one of the specified locations directly. The JDBC driver had this problem in #38521 ### Component(s) FlightRPC -- 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: issues-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
