Open kou opened 1 year ago
At the least, we need to be better about errors, including showing which RPC exactly failed
Hmm, it seems that Ballista returns a location in the FlightEndpoint that can't actually handle the request. The raw C++ implementation is ignoring the location info. As it stands, I think this means Ballista is implementing the protocol wrongly.
I put up a PR to add more context to this kind of error, but otherwise I think the fix should go on the Ballista side.
Ballista https://arrow.apache.org/ballista/ uses Flight SQL for protocol.
https://arrow.apache.org/ballista/user-guide/flightsql.html#a-name-tool-use-the-driver-in-your-favorite-data-tool is the connection information.
(We can use docker-compose to run Ballista cluster on local: https://arrow.apache.org/ballista/user-guide/deployment/docker-compose.html )
Here is a C program that connects to Ballista by ADBC with Flight SQL driver implemented in Go:
FYI: Here is a Ruby version:
But the program is failed with:
I don't know why but I think that Flight SQL driver may send a Flight SQL request that isn't supported Ballista yet.
FYI: We can access to Ballista with raw Apache Arrow Flight SQL C++ implementation: