Test Result : PlannerSuite

0 failures (±0)
45 tests (±0)
Took 6.2 sec.

All Tests

Test nameDurationStatus
CollectLimit can appear in the middle of a plan when caching is used0.11 secPassed
Do not analyze subqueries twice72 msPassed
EnsureRequirements adds sort after full outer sort merge join3 msPassed
EnsureRequirements adds sort when required ordering isn't a prefix of existing ordering1 msPassed
EnsureRequirements adds sort when there is no existing ordering1 msPassed
EnsureRequirements does not eliminate Exchange with different partitioning0 msPassed
EnsureRequirements eliminates Exchange if child has same partitioning1 msPassed
EnsureRequirements for sort operator after left outer sort merge join4 msPassed
EnsureRequirements for sort operator after right outer sort merge join3 msPassed
EnsureRequirements should not repartition if only ordering requirement is unsatisfied11 msPassed
EnsureRequirements should respect ClusteredDistribution's num partitioning1 msPassed
EnsureRequirements skips sort when either side of join keys is required after inner SMJ7 msPassed
EnsureRequirements skips sort when key order of a parent SMJ is propagated from its child SMJ8 msPassed
EnsureRequirements skips sort when required ordering is prefix of existing ordering1 msPassed
EnsureRequirements skips sort when required ordering is semantically equal to existing ordering1 msPassed
EnsureRequirements with child partitionings with different numbers of output partitions5 msPassed
EnsureRequirements with compatible child partitionings that do not satisfy distribution12 msPassed
EnsureRequirements with compatible child partitionings that satisfy distribution7 msPassed
InMemoryRelation statistics propagation0.87 secPassed
PartitioningCollection0.46 secPassed
Reuse exchanges4 msPassed
SPARK-11390 explain should print PushedFilters of PhysicalRDD1.3 secPassed
SPARK-23375: Cached sorted data doesn't need to be re-sorted0.93 secPassed
SPARK-24242: RangeExec should have correct output ordering and partitioning99 msPassed
SPARK-24495: EnsureRequirements can return wrong plan when reusing the same key in join1 msPassed
SPARK-24500: create union with stream of children0.41 secPassed
SPARK-24556: always rewrite output partitioning in ReusedExchangeExec and InMemoryTableScanExec0.34 secPassed
SPARK-25278: physical nodes should be different instances for same logical nodes43 msPassed
SPARK-26812: wrong nullability for complex datatypes in union2 msPassed
TakeOrderedAndProject can appear in the middle of plans0.2 secPassed
TakeOrderedAndProjectExec appears only when number of limit is below the threshold94 msPassed
aliases in the aggregate expressions should not introduce extra shuffle98 msPassed
aliases in the object hash/sort aggregate expressions should not introduce extra shuffle0.19 secPassed
aliases in the project should not introduce extra shuffle0.11 secPassed
aliases to expressions should not be replaced0.1 secPassed
collapse adjacent repartitions87 msPassed
count distinct is partially aggregated6 msPassed
count is partially aggregated12 msPassed
efficient terminal limit -> sort should use TakeOrderedAndProject68 msPassed
mixed aggregates are partially aggregated7 msPassed
mixed aggregates with same distinct columns0.15 secPassed
reorder should handle duplicate expressions2 msPassed
sizeInBytes estimation of limit operator for broadcast hash join optimization0.16 secPassed
terminal limit -> project -> sort should use TakeOrderedAndProject52 msPassed
terminal limits that are not handled by TakeOrderedAndProject should use CollectLimit32 msPassed