FlightSQL operations and limits
FlightSQL’s documented preview contract covers Arrow query results and metadata discovery inside a trusted deployment. Writes, prepared statements, transactions and cross-tenant authorization guarantees remain outside that contract. Treat these limits per operation; a successful connectivity query does not establish isolation, failover or recent-row visibility.
Query surface
Section titled “Query surface”- statement queries using DuckDB SQL;
- catalog, schema, table, and table-type discovery;
- table schemas and selected SQL capability metadata; and
- TLS transport.
Prepared statements, SQL updates, DDL, transactions, and seamless connection failover are outside the supported FlightSQL contract. Treat this interface as a preview within a trusted deployment; cross-tenant authorization and revocation are not yet supported guarantees. Use PGWire or managed DuckDB for supported DDL and writes.
The complete cross-interface boundary is in the compatibility matrix.
Discovery
Section titled “Discovery”FlightSQL clients can request:
- catalogs;
- database schemas;
- tables, optionally with serialized Arrow schemas;
- table types; and
- supported SQL information fields.
Do not rely on this preview endpoint for isolation between untrusted tenants.
Known limits
Section titled “Known limits”- Use this interface for read queries; writes are outside the supported contract.
- SQL uses DuckDB syntax and semantics.
- Prepared statements and statement updates are outside the release contract.
- A client must reconnect to a healthy endpoint after connection loss; seamless FlightSQL failover is not supported.
- Client and BI-tool compatibility must be validated for the exact driver version and workflow.
FlightSQL does not currently promise access to all unpublished recent rows visible through PGWire. A live subscription and a SQL query can return different data.