Test Result : DynamicPartitionPruningSuiteAEOn

0 failures (±0)
22 tests (±0)
Took 1 min 42 sec.

All Tests

Test nameDurationStatus
DPP should not be rewritten as an existential join0.17 secPassed
DPP triggers only for certain types of query0.46 secPassed
Make sure dynamic pruning works on uncorrelated queries1.8 secPassed
Plan broadcast pruning only when the broadcast can be reused2.6 secPassed
avoid reordering broadcast join keys to match input hash partitioning4.4 secPassed
broadcast a single key in a HashedRelation6.2 secPassed
broadcast multiple keys in a LongHashedRelation5.2 secPassed
broadcast multiple keys in an UnsafeHashedRelation4 secPassed
cleanup any DPP filter that isn't pushed down due to expression id clashes21 secPassed
cleanup any DPP filter that isn't pushed down due to non-determinism0.18 secPassed
different broadcast subqueries with identical children3.9 secPassed
dynamic partition pruning ambiguity issue across nested joins4.1 secPassed
filtering ratio policy fallback2 secPassed
filtering ratio policy with stats when the broadcast pruning is disabled1.3 secPassed
join key with multiple references on the filtering plan4.5 secPassed
no partition pruning when the build side is a stream3.7 secPassed
partition pruning in broadcast hash joins3.3 secPassed
partition pruning in broadcast hash joins with aliases2.2 secPassed
partition pruning in broadcast hash joins with non-deterministic probe part0.16 secPassed
self-join on a partitioned table should not trigger DPP0.15 secPassed
simple inner join triggers DPP with mock-up tables29 secPassed
static scan metrics1.2 secPassed