Test Result : DynamicPartitionPruningSuiteAEOn

0 failures (±0)
22 tests (±0)
Took 3 min 11 sec.

All Tests

Test nameDurationStatus
DPP should not be rewritten as an existential join0.5 secPassed
DPP triggers only for certain types of query2.3 secPassed
Make sure dynamic pruning works on uncorrelated queries4 secPassed
Plan broadcast pruning only when the broadcast can be reused1.7 secPassed
avoid reordering broadcast join keys to match input hash partitioning10 secPassed
broadcast a single key in a HashedRelation7 secPassed
broadcast multiple keys in a LongHashedRelation8 secPassed
broadcast multiple keys in an UnsafeHashedRelation9.1 secPassed
cleanup any DPP filter that isn't pushed down due to expression id clashes39 secPassed
cleanup any DPP filter that isn't pushed down due to non-determinism0.1 secPassed
different broadcast subqueries with identical children7.4 secPassed
dynamic partition pruning ambiguity issue across nested joins7.5 secPassed
filtering ratio policy fallback6.1 secPassed
filtering ratio policy with stats when the broadcast pruning is disabled3.9 secPassed
join key with multiple references on the filtering plan4.5 secPassed
no partition pruning when the build side is a stream11 secPassed
partition pruning in broadcast hash joins6.7 secPassed
partition pruning in broadcast hash joins with aliases3.5 secPassed
partition pruning in broadcast hash joins with non-deterministic probe part0.68 secPassed
self-join on a partitioned table should not trigger DPP0.31 secPassed
simple inner join triggers DPP with mock-up tables51 secPassed
static scan metrics5.2 secPassed