Apache Doris into Apache Arrow through ADBC over the MySQL wire, using MySQL Connector/ODBC 9.4 (adbcBridge 0.1.0)

[singhpratech]

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 Apache Doris through it as one of 46 databases in a single compatibility workload and wanted to share the entry here, since the quirks it records are Doris-specific.

The first-party flightsql ADBC driver already covers Doris, and the mysql ADBC driver may work over its wire protocol too. This entry is a third, documented route — the MySQL wire through MySQL Connector/ODBC — and records exactly what it needed.

What was verified (Apache Doris 2.1.0, MySQL 5.7.99 wire, FE + BE in one container; driver: MySQL Connector/ODBC 9.4):

• Linux: PASS
• macOS arm64: PASS with MySQL Connector/ODBC 26.7.1 (Oracle's arm64 binary, iODBC); FAIL through MariaDB Connector/ODBC 3.2.9 — the server NPEs on its server-side prepared INSERT and rejects the _binary '<raw bytes>' literal its PREPONCLIENT=1 path inlines
• Windows x64: PASS (MySQL Connector/ODBC 26.7.1 + NO_SSPS=1); through 8.4.0 the same entry failed only the non-BMP text check — héllo 🚀 stored byte-exact, read back as héllo ??? on every read path including pyodbc, because 8.4.0 substitutes ? for a non-BMP character before either C type sees it

What the compatibility entry records: Doris reports no transaction support (SQL_TC_NONE), so _binary parameter literals are rewritten as text and NO_SSPS=1 is required — the FE prepares only a point SELECT on a store_row_column unique-key table or an INSERT, and a server-side prepared INSERT executes only for parameters bound from SQL_C_CHAR or to a matching non-character SQL type — a character parameter bound from any other C type, SQL_C_WCHAR included, gets a bare NullPointerException from the FE. Every OLAP table has to declare how its rows are distributed, so generated ingest DDL appends DISTRIBUTED BY RANDOM BUCKETS AUTO plus enable_duplicate_without_keys_by_default, without which Doris refuses any table whose first column is TEXT/STRING (what a generated string column is), FLOAT or DOUBLE; a leading VARCHAR(n) is accepted. Keyed on @@version_comment since version() is a bare MySQL number. No binary column type, no DOUBLE PRECISION spelling; ANSI_QUOTES is accepted but ignored, so identifiers are backtick-quoted. Ingest 2.2k rows/s — an INSERT is a load transaction whatever it carries, so multi-row batching is worth ~300x (7 rows/s without it); fetch 1.36M rows/s. Full entry: docs/COMPATIBILITY.md.

Trying it (Python; Rust, Go, Java and C# are on the docs site):

pip install adbcbridge

import adbcbridge
with adbcbridge.connect(uri="Driver=MySQL ODBC 9.4 Unicode Driver;Server=127.0.0.1;Port=9030;User=root;Database=demo;NO_SSPS=1") as conn:
    with conn.cursor() as cur:
        cur.execute("SELECT ...")
        table = cur.fetch_arrow_table()   # a pyarrow.Table

Links: repository · docs · upstream notes · PyPI

It is a 0.1.0. If the entry says something wrong about Doris, 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.

[singhpratech]

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 adbc_ingest, GetTableSchema, GetObjects, read back) through the ADBC Driver Foundry's native MySQL ADBC driver (0.6.0) and through adbcBridge over MySQL Connector/ODBC, against the Doris all-in-one image.

Native driver: stops at connect with Error 1105: errCode = 2, detailMessage = Only support prepare SelectStmt or InsertStmt now; it prepares a statement on connect that Doris's prepared-statement support does not cover.
ODBC path: all seven steps pass (Connector/ODBC with server-side prepared statements off, as the entry notes already say).

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/