Support standard Filter v2 functions - #13
Merged
Merged
Conversation
rustyconover
force-pushed
the
fix/dictionary-not-in-serialization
branch
from
September 10, 2026 23:34
2d2ed17 to
4208505
Compare
rustyconover
changed the title
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.
Completes the Filter v2 producer implementation for
vgi.duckdb.standard.v1.starts_with,ends_with,contains, andlist_containsusing canonical wire namesValidated on EC2 with GCC 14: release build green, 233 Filter-v2 assertions green, exact dictionary regression green, and live plans show all four standard functions pushed while unsupported
lengthremains residual. Full GitHub integration is running.