Skip to content

perf: extend compact IN-list pruning to ordered types #25012

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kumarUjjawal merged 2 commits into from
Sep 9, 2026
Merged

perf: extend compact IN-list pruning to ordered types #25012

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1576b03
perf: extend compact IN-list pruning to ordered types
kumarUjjawal Sep 7, 2026
fce561f
test: cover primitive IN-list NULL semantics
kumarUjjawal Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions datafusion/common/src/config.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1392,12 +1392,14 @@ config_namespace! {
/// rewrite; other predicates and Bloom-filter pruning remain available.
///
/// Within the cap, nonempty lists of at most 20 values use the existing
/// per-value rewrite. Larger literal string lists on a string column use
/// a compact representation, for both `IN` and `NOT IN`, including lists
/// with NULL members. `NOT IN` with NULL and all-NULL `IN` lists cannot
/// match any rows. Other lists retain the existing per-value rewrite, so
/// raising the cap can make those predicates expensive to build and
/// evaluate.
/// per-value rewrite. Larger literal lists use a compact representation
/// when the column type is string, variable-length binary, integer,
/// decimal, date, time, timestamp, or duration. This applies to both `IN`
/// and `NOT IN`, including lists with NULL members. `NOT IN` with NULL and
/// all-NULL `IN` lists cannot match any rows. Compact lists containing NULL
/// do not use the fully-matched-row-group optimization. Floating-point and
/// other lists retain the existing per-value rewrite, so raising the cap
/// can make those predicates expensive to build and evaluate.
///
/// Defaults to 20.
pub max_in_list_size: usize, default = 20
Expand Down
Loading