Test Result : PlannerSuite

0 failures
56 tests
Took 1.3 sec.

All Tests

Test nameDurationStatus
Change the number of partitions to zero when a range is empty (whole-stage-codegen off)9 msPassed
Change the number of partitions to zero when a range is empty (whole-stage-codegen on)21 msPassed
CollectLimit can appear in the middle of a plan when caching is used9 msPassed
Do not analyze subqueries twice18 msPassed
EnsureRequirements adds sort after full outer sort merge join2 msPassed
EnsureRequirements adds sort when required ordering isn't a prefix of existing ordering0 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 join2 msPassed
EnsureRequirements for sort operator after right outer sort merge join1 msPassed
EnsureRequirements should not repartition if only ordering requirement is unsatisfied1 msPassed
EnsureRequirements should respect ClusteredDistribution's num partitioning0 msPassed
EnsureRequirements skips sort when either side of join keys is required after inner SMJ4 msPassed
EnsureRequirements skips sort when key order of a parent SMJ is propagated from its child SMJ5 msPassed
EnsureRequirements skips sort when required ordering is prefix of existing ordering0 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 distribution1 msPassed
EnsureRequirements with compatible child partitionings that satisfy distribution1 msPassed
InMemoryRelation statistics propagation0.13 secPassed
PartitioningCollection50 msPassed
Reuse exchanges3 msPassed
SPARK-11390 explain should print PushedFilters of PhysicalRDD0.17 secPassed
SPARK-24242: RangeExec should have correct output ordering and partitioning32 msPassed
SPARK-24495: EnsureRequirements can return wrong plan when reusing the same key in join1 msPassed
SPARK-24500: create union with stream of children33 msPassed
SPARK-24556: always rewrite output partitioning in ReusedExchangeExec and InMemoryTableScanExec0.16 secPassed
SPARK-25278: physical nodes should be different instances for same logical nodes11 msPassed
SPARK-26812: wrong nullability for complex datatypes in union1 msPassed
SPARK-27485: EnsureRequirements.reorder should handle duplicate expressions0 msPassed
SPARK-33399: No extra exchanges in case of [Inner Join -> Project with aliases -> HashAggregate]27 msPassed
SPARK-33399: alias handling should happen properly for RangePartitioning11 msPassed
SPARK-33399: alias handling should happen properly for SinglePartition10 msPassed
SPARK-33399: aliased should be handled properly for partitioning and sortorder involving complex expressions43 msPassed
SPARK-33399: aliases should be handled properly in HashPartitioning36 msPassed
SPARK-33399: aliases should be handled properly in PartitioningCollection output partitioning38 msPassed
SPARK-33400: Normalization of sortOrder should take care of sameOrderExprs36 msPassed
SPARK-33758: Prune unnecessary output partitioning34 msPassed
TakeOrderedAndProject can appear in the middle of plans12 msPassed
TakeOrderedAndProjectExec appears only when number of limit is below the threshold.22 msPassed
aliases in the aggregate expressions should not introduce extra shuffle34 msPassed
aliases in the object hash/sort aggregate expressions should not introduce extra shuffle66 msPassed
aliases in the project should not introduce extra shuffle30 msPassed
aliases in the sort aggregate expressions should not introduce extra sort33 msPassed
aliases to expressions should not be replaced36 msPassed
collapse adjacent repartitions5 msPassed
count distinct is partially aggregated4 msPassed
count is partially aggregated6 msPassed
efficient terminal limit -> sort should use TakeOrderedAndProject10 msPassed
mixed aggregates are partially aggregated4 msPassed
mixed aggregates with same distinct columns55 msPassed
sizeInBytes estimation of limit operator for broadcast hash join optimization48 msPassed
sort order doesn't have repeated expressions35 msPassed
terminal limit -> project -> sort should use TakeOrderedAndProject12 msPassed
terminal limits that are not handled by TakeOrderedAndProject should use CollectLimit7 msPassed