Repository navigation
Embed the Haybarn 2.0 engine in the example worker - #12
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the example worker's embedded engine (
ExpressionFilterEvaluator, which evaluates pushed expression filters) fromfarm.query.haybarn:haybarn_jdbc:1.5.4-rc1to2.0.0-rc8(Haybarn 2.0 / DuckDB 2.0 engine). That is the only JDBC reference in the repo; the publishedvgicore stays engine-free. The CLAUDE.md note is updated to match.rc8 note: the Haybarn engine is at rc9, but
haybarn_jdbchas not been re-released at rc9.2.0.0-rc8is the latest on Maven Central.Adaptations: none needed. The 2.0 client keeps the
farm.query.haybarnpackage, thejdbc:haybarn:URL andDuckDBConnection.registerArrowStream.INSTALL spatial FROM coreresolves forv2.0.0. The rc8 jar ships linux amd64/arm64, macOS arm64 and windows amd64 natives. Platform change: 1.5.4-rc1 shippedosx_universal, so Intel macOS can no longer run the example worker's expression-filter evaluator on rc8. The publishedvgicore is unaffected.Tested on EC2 Linux arm64, Temurin JDK 25.0.5:
./gradlew test :vgi:javadoc :vgi-example-worker:installDist: 805 tests, 0 failures, 14 skipped. That matches the 1.5.4-rc1 baseline exactly. The installed worker bundleshaybarn_jdbc-2.0.0-rc8.jar.ci/run-integration.sh(launch lane), using a native runner built on the host from CI's pinnedVGI_REF(7b1e1fb, Clang): 334 cases and 12521 assertions executed, 33 skipped. That is identical tomain's launch lane.expression_filter.testpasses; the 1require spatialskip is a runner-side skip, the same as onmain.main(334/333/330 cases).version()=v2.0.0 2dc3a8066b, spatial install/load,&&andlist_contains.🤖 Generated with Claude Code