Open jmao-denver opened 1 month ago
It looks like adbc_driver_flightsql
first tries doAction / CreatePreparedStatement / ActionCreatePreparedStatement "select from crypto", but then falls back to getFlightInfo / CommandStatementQuery "select from crypto".
It does seem a bit strange that the default behavior is to go the prepared statement route even when the query is ad-hoc? For reference, the sequence diagrams here show the ad-hoc vs prepared statement: https://arrow.apache.org/docs/format/FlightSql.html#sequence-diagrams
Currently, both JDBC and ADBC driver bindings execute ALL queries (prepared or not) through the AFS PreparedStatement endpoints. See https://github.com/apache/arrow-adbc/issues/2040#issuecomment-2305242075
Describe the bug, including details regarding any error messages, version, and platform.
We (Deephaven Data Labs) have a simple FlightSQL implementation that doesn't support PreparedStatement with the understanding that executing ad hoc queries should be possible with JDBC's Statement.execute()/executeQuery(). However, the following test case failed with an exception that indicates the driver chooses to use PreparedStatement anyways. Note that the ADBC driver for FlightSQL (Python) uses CommandStatementQuery for the same use case.
This Python script runs OK against the same server.
version: Arrow 13.0.0 platform: MacOS 14.5
Component(s)
Java