Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0.0
-
None
-
None
Description
Currently, for dynamic partition pruning in Spark, if a small table generates partition info for more than one partition columns, multiple operator trees are created, which all start from the same table scan op, but have different spark partition pruning sinks.
As an optimization, we can combine these op trees and so don't have to do table scan multiple times.
Attachments
Attachments
Issue Links
- is related to
-
HIVE-9152 Dynamic Partition Pruning [Spark Branch]
- Closed
- links to