← All databases

GreptimeDB into Apache Arrow with ADBC

GreptimeDB 1.1.4 (MySQL 8.4.2 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=14002;Database=public;User=greptime;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=14002;Database=public;User=greptime;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 GreptimeDB 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

time-series store, driven over its MySQL wire (4002); its PostgreSQL wire (4003) cannot be reached at all — psqlodbc's connect handshake asks for show transaction_isolation, which GreptimeDB does not implement (only SHOW TRANSACTION ISOLATION LEVEL), so SQLDriverConnect fails as it does for H2.

What this stack needed

• Every table needs a TIME INDEX column, so generated ingest DDL appends one that defaults to the insert time (ddl_extra_column: greptime_timestamp TIMESTAMP(3) TIME INDEX DEFAULT CURRENT_TIMESTAMP) plus append_mode (ddl_table_options) — outside append mode rows sharing a timestamp are merged; prepared-statement metadata types every parameter as a string and then rejects it, so NO_SSPS=1 plus the Databend _binary quirk; no DOUBLE PRECISION type name and no ANSI_QUOTES (backtick-quoted identifiers); ingest 181k rows/s (156k with array binding), fetch 989k rows/s

Native ADBC driver, compared

GreptimeDB 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 GreptimeDB; 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