API, Core, Spark: Add CONTAINS and NOT_CONTAINS expressions - #17906
Draft
shiva-imc wants to merge 1 commit into
Draft
API, Core, Spark: Add CONTAINS and NOT_CONTAINS expressions#17906shiva-imc wants to merge 1 commit into
shiva-imc wants to merge 1 commit into
Conversation
Spark emits a DSv2 CONTAINS predicate for contains() but Iceberg has no matching operation, so predicates decidable from partition values fall back to row-level scans. Evaluation is exact where complete values exist and conservative from truncated bounds, mirroring STARTS_WITH.
shiva-imc
force-pushed
the
contains-expressions
branch
from
August 31, 2026 16:24
a4c83aa to
2093fdd
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
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.
Add
CONTAINS/NOT_CONTAINS(substring match on string terms) to the expression API, alongside the existingSTARTS_WITH/NOT_STARTS_WITH.Spark emits a DSv2
CONTAINSpredicate for thecontains()function, but Iceberg has no matching operation, so the predicate is dropped atSparkV2Filtersand any operation that could otherwise be answered from metadata falls back to row-level scans. The motivating case:DELETE FROM t WHERE contains(part_col, 'x')on an identity-partitioned column is decidable exactly from partition values, but today plans as a full copy-on-write scan-and-rewrite. With this change it plans as a metadata-only delete.