← All databases

StarRocks into Apache Arrow with ADBC

StarRocks 4.1.4 (MySQL 8.0.33 wire), read and written through adbcBridge — the ADBC driver that loads the database's ODBC driver — verified on Linux, macOS arm64 and Windows x64. Everything below is the compatibility matrix's record for this row.

Status

Driver and connection string

ODBC driver

MySQL Connector/ODBC 9.4 (MySQL wire)

Wire

MySQL wire

adbcBridge

0.1.1 (release)

The connection string the matrix used, as the connection strings reference records it (MySQL wire); {drv} is the driver library or its name from odbcinst.ini, and the host, port and credentials are the test server's.

Driver={drv};Server=127.0.0.1;Port=19030;User=root;NO_SSPS=1;{plugin_dir}

Python

import adbcbridge

# {drv}: the ODBC driver library (path), or its name from odbcinst.ini
conn = adbcbridge.connect(uri="Driver={drv};Server=127.0.0.1;Port=19030;User=root;NO_SSPS=1;")
with conn.cursor() as cur:
    cur.execute("SELECT * FROM my_table")
    table = cur.fetch_arrow_table()      # pyarrow.Table

Polars and pandas

import polars as pl, pandas as pd

df = pl.read_database("SELECT * FROM my_table", connection=conn)   # Polars, Arrow-native
pdf = pd.read_sql("SELECT * FROM my_table", conn)                   # pandas 2.2+, ADBC connection

pip install adbcbridge brings the driver library; the StarRocks ODBC driver is installed the way its vendor documents, then named in Driver=. Rust, Go, C# and Java use the same connection string through their ADBC driver managers — see the docs.

What the matrix recorded

MPP columnar warehouse: it prepares nothing but SELECT, so the connector runs with NO_SSPS=1, and the _binary date/timestamp/binary literals it then emits are sent as ordinary quoted text instead (temporal_binary_param_as_varchar, restored -- it had been dead code since a bad merge); MySQL type names rejected in ingest DDL, so it uses standard SQL names, and the portable fallback for a double is now DOUBLE, not the ISO DOUBLE PRECISION, which StarRocks does not parse; no ANSI_QUOTES mode at all, so identifiers are quoted with backticks (the driver already asks for SQL_IDENTIFIER_QUOTE_CHAR); DECIMAL(10,3) described at MySQL's display width (12,3); ingest 4.8k rows/s -- every INSERT is a load transaction costing a flat ~100 ms of server-side work (10 rows/s for any client sending one row per statement), so the multi-row batching is worth 480x here (pyodbc, which has no such batching, cannot ingest here at all); fetch 1.80M rows/s

Native ADBC driver, compared

StarRocks speaks the MySQL wire protocol, so the ADBC Driver Foundry's native MySQL ADBC driver (0.6.0) can be pointed at it too. On 2026-09-05 the same seven-step ADBC workload (connect, SELECT 1, DDL and inserts and a read, a 1,000-row adbc_ingest, table schema, catalog listing, read back) ran through both:

Where the native driver stops it is by design of that driver, not a defect of StarRocks; the full table for all 28 wire-compatible databases, with each first error, is in the note.

Read next

• Where the native PostgreSQL and MySQL ADBC drivers stop on wire-compatible databases
• What MySQL Connector/ODBC does to a DATETIME(6), and six other findings
• A Unicode string parameter cannot reach a MySQL-wire warehouse's prepare