Test Result : DynamicPartitionPruningSuiteAEOn

0 failures (±0)
24 tests (±0)
Took 23 sec.

All Tests

Test nameDurationStatus
DPP should not be rewritten as an existential join60 msPassed
DPP triggers only for certain types of query0.12 secPassed
Make sure dynamic pruning works on uncorrelated queries0.73 secPassed
Plan broadcast pruning only when the broadcast can be reused0.4 secPassed
SPARK-32509: Unused Dynamic Pruning filter shouldn't affect canonicalization and exchange reuse0.36 secPassed
SPARK-32659: Fix the data issue when pruning DPP on non-atomic type2 secPassed
avoid reordering broadcast join keys to match input hash partitioning1.6 secPassed
broadcast a single key in a HashedRelation2.3 secPassed
broadcast multiple keys in a LongHashedRelation1.8 secPassed
broadcast multiple keys in an UnsafeHashedRelation1.8 secPassed
cleanup any DPP filter that isn't pushed down due to expression id clashes0.39 secPassed
cleanup any DPP filter that isn't pushed down due to non-determinism29 msPassed
different broadcast subqueries with identical children1.7 secPassed
dynamic partition pruning ambiguity issue across nested joins1.4 secPassed
filtering ratio policy fallback0.65 secPassed
filtering ratio policy with stats when the broadcast pruning is disabled0.69 secPassed
join key with multiple references on the filtering plan1.5 secPassed
no partition pruning when the build side is a stream1.6 secPassed
partition pruning in broadcast hash joins1.2 secPassed
partition pruning in broadcast hash joins with aliases0.92 secPassed
partition pruning in broadcast hash joins with non-deterministic probe part92 msPassed
self-join on a partitioned table should not trigger DPP83 msPassed
simple inner join triggers DPP with mock-up tables0.37 secPassed
static scan metrics0.77 secPassed