RisingWave into Apache Arrow through ADBC, using psqlodbc 16 (adbcBridge 0.1.0) #26850
Replies: 1 comment
|
A follow-up with one new measurement. On 2026-09-05 I ran the same seven-step ADBC workload (connect, SELECT 1, DDL + inserts + read, 1,000-row Native driver: stops at connect. Its type-resolver bootstrap query against Table for all 28 PostgreSQL-wire and MySQL-wire databases, with each native driver's first error: https://adbcbridge.org/notes/native-adbc-drivers-on-wire-compatible-databases/ |
Uh oh!
There was an error while loading. Please reload this page.
adbcBridge is a small Apache-2.0 ADBC driver written in C11 that loads an ODBC driver and exposes it through the Arrow ADBC C ABI: block-cursor reads straight into Arrow record batches, bulk ingest, metadata, partitioned parallel reads. I ran RisingWave through it as one of 46 databases in a single compatibility workload and wanted to share the entry here.
What was verified (RisingWave 3.0; driver: psqlodbc 16)
What the compatibility entry records: no
adbc.odbc.*quirks, but the entry sets psqlodbc'sUseServerSidePrepare=0: psqlodbc names every server-side statement_PLAN0x<statement-handle address>and RisingWave keeps the name after the handle is freed, so the nextSQLPrepareunder a reused name failsXX000 ... Duplicated statement name(the ordinary allocate/prepare/execute/free loop hits it on its second query);version()names RisingWave, so the PostgreSQL array-ingest form stays off (verified); server side: the parser takes no length, precision or scale on a column type (VARCHAR,NUMERICdeclared unqualified;FLOAT(p)is the one modifier it does take) and a write reaches a scan only at the next barrier (1 s by default), so reads followFLUSH, which forces one straight away; ingest 31.9k rows/s (35.3k with array binding), fetch 1.00M rows/s. Full entry: docs/COMPATIBILITY.md.The
postgresqlADBC driver may also work with RisingWave over its wire protocol; this path goes through psqlodbc and records exactly what it needed, so it is a second, documented route rather than a replacement.Trying it (Python; Rust, Go, Java and C# are on the docs site):
Links: repository · docs · upstream notes · PyPI
It is a 0.1.0. If the entry says something wrong about RisingWave, or you run a version or driver I didn't, an issue on the repository with the details is the most useful thing you could send.
All reactions