Skip to content
Query.Farm
Talk with Us

What's new

These docs describe 0.26.1, the current release on Maven Central. The artifact is pre-1.0, so minor versions still carry breaking changes.

0.26.x — a Java client

Section titled “0.26.x — a Java client”

0.26.0 made the client able to build the payloads it sends, so a Java program can call a VGI worker directly rather than going through DuckDB. 0.26.1 followed with vgirpc 0.22.0, an HTTP client, and a fix for worker logs being lost across an HTTP stream.

The client arrived over 0.25.0–0.26.1 and is the newest part of the artifact; it has a reference page but no guide yet.

0.25.x — the client, and externalized batches

Section titled “0.25.x — the client, and externalized batches”

0.25.0 introduced the client. 0.25.1 fixed it dropping externalized batches — the ones handed over through the side channel rather than inline, which is exactly the path a large result takes.

0.24.x — per-catalog attach options

Section titled “0.24.x — per-catalog attach options”

0.24.0 added per-catalog attach options and a gated ATTACH that answers rather than failing opaquely, so a worker can require and validate options at attach time. 0.24.1 was dependency bumps.

Two build settings changed shape over this range

If you are upgrading from well before 0.24, re-check the build file against Running a worker. -parameters and the two --add-opens / --enable-native-access JVM flags are load-bearing, and the first of them fails silently — your arguments become arg0 and named-argument calls stop resolving while everything else keeps working.

A note on the examples

Section titled “A note on the examples”

The runnable examples this documentation embeds were pinned to farm.query:vgi:0.1.0 until recently — twenty-five releases behind. Bumping them to 0.26.1 turned up exactly one break in seven examples, which says the API has been remarkably stable: BufferingFinalizeProducer now exposes storage() as a method rather than a field, because the accessor re-binds the storage view when a producer is resumed after an HTTP continuation.

Next steps

Section titled “Next steps”