PruneFileSourcePartitions Logical Optimization¶
Filter logical operator over a "pruned"
LogicalRelation with the HadoopFsRelation of a Hive partitioned table (with a PrunedInMemoryFileIndex.md[PrunedInMemoryFileIndex]).
=== [[apply]] Executing Rule --
apply( plan: LogicalPlan): LogicalPlan
apply PhysicalOperation.md#unapply[destructures the input logical plan] into a tuple of projection and filter expressions together with a leaf logical operator.
apply transforms LogicalRelation.md[LogicalRelations] with a HadoopFsRelation and a CatalogFileIndex (i.e. for Hive tables) when there are filter expressions defined and the Hive table is partitioned.
apply resolves partition column references (by requesting the logical operator to spark-sql-LogicalPlan.md#resolve[resolve partition column attributes to concrete references in the query plan]) and excludes spark-sql-Expression-SubqueryExpression.md#hasSubquery[subquery expressions].
If there are no predicates (filter expressions) left for partition pruning,
apply simply does nothing more and returns the input logical query untouched.
apply replaces the FileIndex in the HadoopFsRelation with the
PrunedInMemoryFileIndex and the CatalogStatistics.md#sizeInBytes[total size] statistic to the PartitioningAwareFileIndex.md#sizeInBytes[PrunedInMemoryFileIndex's].
In the end,
apply creates a
Filter logical operator (with the "pruned"
LogicalRelation as a child operator and all the filter predicate expressions combined together with
And expression) and makes it a child operator of a Project.md[Project] operator.
apply is part of the Rule abstraction.