Fix spatial filter WKB rendering - #6
Merged
Merged
Conversation
rustyconover
force-pushed
the
fix/spatial-filter-wkb-rendering
branch
from
September 10, 2026 23:17
4d45eb1 to
aeb9626
Compare
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
1 participant
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.
Render geoarrow.wkb columns and literals as DuckDB geometry values before evaluating pushed spatial predicates, and use the canonical
st_intersects_extentfunction instead of the array-only&&operator. Adds a wire-level Filter v2 regression test.