You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the usage question you have. Please include as many useful details as possible.
Hello folks,
I am connecting to my flight server using Arrow Flight JDBC driver(12.0.0). As per the sequence diagram for executing a prepared statement, the DoGET method is invoked for each endpoint in the FlightInfo. However, I am unable to get this working if I provide multiple locations in the FlightInfo response. The client iterates on the endpoints but always connects to the host & port configured as part of the JDBC connect string and does not switch to the location(s) passed in the FlightInfo.
JDBC URL:
jdbc:arrow-flight-sql://primaryendpoint:50051
Below is a sample FlightInfo object. For this, I expect the client to connect to secondaryendpoint:50051 for streaming data but the DoGet calls are executed on the primaryendpoint:50051 location which is part of the initial JDBC connect string.
Any insights on this behavior and how can I get the client to switch to the locations for the DoGet operation? Is my understanding of the FlightRPC patterns correct?
Component(s)
FlightRPC, Java
The text was updated successfully, but these errors were encountered:
There's a partial PR listed in that issue - if you're interested in taking it across the finish line I'd be happy to review and/or answer any questions.
Describe the usage question you have. Please include as many useful details as possible.
Hello folks,
I am connecting to my flight server using Arrow Flight JDBC driver(12.0.0). As per the sequence diagram for executing a prepared statement, the DoGET method is invoked for each endpoint in the FlightInfo. However, I am unable to get this working if I provide multiple locations in the FlightInfo response. The client iterates on the endpoints but always connects to the host & port configured as part of the JDBC connect string and does not switch to the location(s) passed in the FlightInfo.
JDBC URL:
Below is a sample FlightInfo object. For this, I expect the client to connect to
secondaryendpoint:50051
for streaming data but the DoGet calls are executed on theprimaryendpoint:50051
location which is part of the initial JDBC connect string.Any insights on this behavior and how can I get the client to switch to the locations for the DoGet operation? Is my understanding of the FlightRPC patterns correct?
Component(s)
FlightRPC, Java
The text was updated successfully, but these errors were encountered: