POC Rewrite bloom filter pruning predicate logic in terms of intervals

[alamb]

Which issue does this PR close?

This is related to apache#7821 and the hope of a high level unification of PruningPredicate and the interval arithmetic (I thought there was a ticket, but I can't find it)

Rationale for this change

Basically DataFusion has two types of range analysis -- the Interval based analysis used in selectivity analysis and the PruningPrediate based rewrite used for pruning row groups in parquet.

apache#7821 adds a BloomFilterPredicate in the style of PruningPredicate. However, this only supports binary expressions (col = <const>) and AND / OR and is entirely separate from statistics based pruning. This means that predicates like col IN (...) and IS NOT NULL may not be completely supported.

I am pretty sure I could express the same analysis in terms of Intervals, which:

1. Is more general (as we add support for range analysis in predicates, the bloom filtering will support them as well)
2. Is more concise (less code)
3. and this would serve as a proof of concept for using the Intervals for the more general PredicatePruning.

What changes are included in this PR?

1. Express the application of Bloom filters using interval arithmetic rather than partial expression evaluation.

Are these changes tested?

Yes, existing tests

Are there any user-facing changes?

Not really.

[alamb]

I am quite pleased with this logic. What it does is to rewrite the predicate String@0 = Hello_Not_Exists AND 1 = 1 is rewritten to false AND false and the interval analysis determines that expression is always false:

Evaluating. self.predicate_expr: String@0 = Hello_Not_Exists AND 1 = 1
   rewritten false AND 1 = 1
   interval result: [false, false]
lower: IntervalBound { value: Boolean(false), open: false }
upper: IntervalBound { value: Boolean(false), open: false }

However it seems I need to update the interval analysis so that OR is handled as OR gives a "unknown" for the bounds:

Evaluating. self.predicate_expr: String@0 = Hello_Not_Exists OR String@0 = Hello_Not_Exists2
   rewritten false OR false
   interval result: (NULL, NULL)
lower: IntervalBound { value: NULL, open: true }
upper: IntervalBound { value: NULL, open: true }

[alamb]

Added support for OR here: apache#7884

[crepererum]

I agree w/ you that pruning analysis and interval arithmetic should be implemented ONCE, ideally using an interface that both arrow and datafusion can use.

[alamb]

I agree w/ you that pruning analysis and interval arithmetic should be implemented ONCE, ideally using an interface that both arrow and datafusion can use.

I filed apache#7887 to track this idea