Embed the Haybarn 2.0 engine in the example worker

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: 2 people

CLAUDE.md

@@ -1176,7 +1176,7 @@ without a C++ build:
     expose the SQL.
   - **Evaluator (worker):** `example/table/ExpressionFilterEvaluator` evaluates
     the predicates against each batch via an embedded **haybarn_jdbc** engine
-    (Maven Central `farm.query.haybarn:haybarn_jdbc:1.5.3` + `arrow-c-data`),
+    (Maven Central `farm.query.haybarn:haybarn_jdbc:2.0.0-rc8`, Haybarn 2.0 + `arrow-c-data`),
     thread-local connection with spatial loaded — the Java analogue of
     vgi-python's `vgi._duckdb` evaluator. Batch is bridged in via the Arrow C
     Data interface (`registerArrowStream`); a registered stream is **single-use**

vgi-example-worker/build.gradle.kts

@@ -10,7 +10,7 @@ dependencies {
     // (spatial &&, list_contains, ...) against emitted batches — mirrors
     // vgi-python's `vgi._duckdb` expression-filter evaluator. arrow-c-data
     // bridges an Arrow batch into the engine via the C Data interface.
-    implementation("farm.query.haybarn:haybarn_jdbc:1.5.4-rc1")
+    implementation("farm.query.haybarn:haybarn_jdbc:2.0.0-rc8")
     // Held at 19.0.0 deliberately: vgi-rpc-java exports arrow-vector/
     // arrow-memory-netty 19.0.0 as `api` deps, and Arrow's Java modules must
     // stay version-consistent on one classpath. Bump this only in lockstep