Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to read data from multiple locations while using Flight SQL JDBC driver #35829

Closed
Srivatzn opened this issue May 30, 2023 · 3 comments
Closed

Comments

@Srivatzn
Copy link

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.

[<pyarrow.flight.FlightEndpoint ticket=<pyarrow.flight.Ticket ticket=b'GET-DATA'> locations=[<pyarrow.flight.Location b'grpc+tcp://secondaryendpoint:50051'>]>]

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

@lidavidm
Copy link
Member

This is not currently implemented in the JDBC driver, correct :/ contributions would be welcome. (I think there was an earlier issue about it, too.)

@lidavidm
Copy link
Member

Duplicate of #34532.

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.

@lidavidm lidavidm closed this as not planned Won't fix, can't repro, duplicate, stale May 30, 2023
@Srivatzn
Copy link
Author

Thanks for the details, David. I will take a look at them. Appreciate your time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants