# Dynamic partition pruning

Glossary, read 10 Nov 2026

**The short answer.** Dynamic partition pruning skips partitions of a large table at runtime using the filter results of a joined smaller table. The Spark setting spark.sql.optimizer.dynamicPartitionPruning.enabled is true by default, since Spark 3.0.0. It cuts the data a query reads without any SQL change.

Pruning only works on partitioned tables where the join key is the partition column, which is common in star-schema queries.

Amazon EMR's release guide documents the feature on its own page, so check whether your baseline had it on.

## A sourced example

Per AWS documentation, dynamic partition pruning is enabled by default from Amazon EMR 5.26.0, and can be switched on in 5.24.0 and 5.25.0 with spark.sql.dynamicPartitionPruning.enabled.

## Sources

- AWS: Optimize Spark performance on Amazon EMR: https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-spark-performance.html (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://sparkaccelerationcompare.com/glossary/dynamic-partition-pruning/
