Rusty Conover
Data infrastructure engineer and founder of Query.Farm. Building DuckDB extensions, scaling data platforms, and writing about what I learn along the way.
Recent Activity
View all →Rusty tackled a variety of integration and compatibility challenges across the DuckDB ecosystem today.
Rusty focused on low-level transport and worker lifecycle improvements across the vgi-rpc-typescript and vgi-rpc-python codebases, with parallel development on private infrastructure.
Rusty spent the day working across two main repositories, with significant activity in private repos as well.
Quack and VGI: Two Approaches to Bringing RPC to DuckDB
Quack — the new client/server protocol extension for DuckDB — was announced today. It's been built since November 2025, almost exactly as long as I've been building VGI. Here's what's interesting, what's surprising, and where the two projects converge and diverge.
DuckDB ↔ Arrow Compatibility: A Status Page
A working status page for the Arrow-related issues and PRs I've filed against duckdb/duckdb — the UNION saga, schema/data disagreements in nested appenders, type fidelity through round-trips, and the bigger question of how defensive the C Data Interface should be.
GeoSilo vs GeoArrow + Byte Stream Split: Two Approaches to Geometry Compression
A detailed comparison of GeoSilo's delta-integer encoding against GeoArrow's columnar float64 layout with Parquet BYTE_STREAM_SPLIT, covering compression ratios, precision tradeoffs, and when each approach wins.
VGI Injector: A Tiny HTTPS Download-and-Execute Binary in Zig
I needed a self-contained binary that downloads a program over HTTPS and exec's it — small enough to run in a FROM scratch container with nothing else. Go and Rust couldn't get small enough. Zig could.
TIME Data Type Compatibility Across Databases
A survey of the TIME data type across 14 databases, comparing supported ranges, maximum values, and whether the special value 24:00:00 is accepted.
Telemetry for DuckDB Extensions Without the Pain
I open-sourced the telemetry client I use across Query.Farm's DuckDB extensions. It's two files, one function call, and it only collects platform and version info.
Releasing vgi-rpc: An RPC Framework Built on Apache Arrow
I built an RPC framework for Python that uses Apache Arrow IPC as the wire format and Python Protocol classes as the interface definition. No .proto files, no codegen — just type annotations.
Acronym-Aware Case Conversions in the DuckDB Inflector Extension
The Inflector extension for DuckDB now supports configurable acronyms, so case conversions preserve terms like HTML, API, and URL as fully uppercase — configured through a native DuckDB setting.
What I've Been Working On
Full activity log →I've been deep in infrastructure and ecosystem work these past three months, from DuckDB compatibility crusades to shipping a complete multi-language RPC framework. The through-line has been systematic stewardship—whether upgrading 27 repositories for DuckDB 1.5 compatibility, contributing upstream enhancements to Apache Arrow across four language implementations, or maintaining stability across a sprawling extension portfolio. Underneath it all, I've also been working on classified initiatives that I can't fully detail here, but let's just say the commit graphs tell an interesting story.
- Orchestrated DuckDB 1.5 compatibility across the Query-farm extension portfolio, opening 40+ PRs to future-proof extensions and standardizing documentation structures while maintaining backward compatibility.
- Contributed upstream to Apache Arrow with custom metadata support for RecordBatch IPC messages and public APIs for dictionary serialization, fixing silent data drops that likely haunted production systems.
- Shipped vgi-rpc ecosystem with production-ready implementations in Python, C++, Go, and TypeScript, complete with unified branding, documentation sites, and Apache 2.0 licensing across the entire suite.