Arrow support in future plans?
@teunbrand is already working on this.
Since Apr 21, 2026.
- Dominant language
- Rust
- Stars
- 554
- Forks
- 30
- Avg merge
- 17h 27m
- Merged PRs (30d)
- 8
Description
Thinking about the reader architecture: have you considered an Arrow-native path via ADBC alongside the existing ODBC reader?
Reasoning: Polars is already the internal DataFrame format, so an AdbcReader could hand Arrow record batches to Polars zero-copy, avoiding the row-by-row accumulation in OdbcReader's ColumnBuilder. Would complement rather than replace ODBC since ADBC driver coverage is narrower, but for backends that ship ADBC drivers it's a cleaner path.
This builds off another feature request (see [330] (https://github.com/posit-dev/ggsql/issues/330) ) .Exasol ships exarrow-rs, an ADBC-compatible Rust driver, on crates.io. So an AdbcReader would unlock Exasol immediately without needing a dialect-specific module. Other warehouses are on the same trajectory (Snowflake, DuckDB, Postgres all have ADBC drivers shipping). Either way I'd love to contribute, but want to align with your team's technical direction!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.