Test Result : DynamicPartitionPruningSuiteAEOn

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

All Tests

Test nameDurationStatus
DPP should not be rewritten as an existential join0.21 secPassed
DPP triggers only for certain types of query0.31 secPassed
Make sure dynamic pruning works on uncorrelated queries1.5 secPassed
Plan broadcast pruning only when the broadcast can be reused1 secPassed
avoid reordering broadcast join keys to match input hash partitioning4.7 secPassed
broadcast a single key in a HashedRelation6 secPassed
broadcast multiple keys in a LongHashedRelation2.6 secPassed
broadcast multiple keys in an UnsafeHashedRelation2.4 secPassed
cleanup any DPP filter that isn't pushed down due to expression id clashes15 secPassed
cleanup any DPP filter that isn't pushed down due to non-determinism85 msPassed
different broadcast subqueries with identical children4.2 secPassed
dynamic partition pruning ambiguity issue across nested joins3.4 secPassed
filtering ratio policy fallback1.6 secPassed
filtering ratio policy with stats when the broadcast pruning is disabled1.5 secPassed
join key with multiple references on the filtering plan5.3 secPassed
no partition pruning when the build side is a stream2.7 secPassed
partition pruning in broadcast hash joins3.5 secPassed
partition pruning in broadcast hash joins with aliases2.4 secPassed
partition pruning in broadcast hash joins with non-deterministic probe part0.2 secPassed
self-join on a partitioned table should not trigger DPP0.14 secPassed
simple inner join triggers DPP with mock-up tables37 secPassed
static scan metrics1.8 secPassed