Optimize NOT IN and != predicates for single-value files #14593
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.
Summary
This PR adds file pruning optimization for
NOT INand!=predicates when a file contains a single distinct value (i.e., whenmin == max).Problem
Currently, InclusiveMetricsEvaluator cannot prune files for
NOT INand!=predicates, even when the file provably contains no matching rows.Solution
When
min == maxand the file has no nulls, we can safely prune if:NOT IN: the single value is in the exclusion list!=: the single value equals the literalTesting
notInandnotEqoptimizationsFixes #14592