Struct EnforceSorting 

pub struct EnforceSorting {}

This rule inspects SortExec’s in the given physical plan in order to remove unnecessary sorts, and optimize sort performance across the plan.

Implementations

impl EnforceSorting

pub fn new() -> Self

Trait Implementations

impl Debug for EnforceSorting

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for EnforceSorting

fn default() -> EnforceSorting

Returns the “default value” for a type.

impl PhysicalOptimizerRule for EnforceSorting

Performs optimizations based upon a series of subrules. Refer to each subrule for detailed descriptions of the optimizations performed: Subrule application is ordering dependent.

Optimizer consists of 5 main parts which work sequentially

1. ensure_sorting Works down-to-top to be able to remove unnecessary SortExecs, SortPreservingMergeExecs add SortExecs if necessary by a requirement and adjusts window operators.
2. parallelize_sorts (Optional, depends on the repartition_sorts configuration) Responsible to identify and remove unnecessary partition unifier operators such as SortPreservingMergeExec, CoalescePartitionsExec follows SortExecs does possible simplifications.
3. replace_with_order_preserving_variants() Replaces with alternative operators, for example can merge a SortExec and a CoalescePartitionsExec into one SortPreservingMergeExec or a SortExec + RepartitionExec combination into an order preserving RepartitionExec
4. sort_pushdown Works top-down. Responsible to push down sort operators as deep as possible in the plan.
5. replace_with_partial_sort Checks if it’s possible to replace SortExecs with PartialSortExec operators

fn optimize( &self, plan: Arc<dyn ExecutionPlan>, config: &ConfigOptions, ) -> Result<Arc<dyn ExecutionPlan>>

Rewrite plan to an optimized form

fn name(&self) -> &str

A human readable name for this optimizer rule

fn schema_check(&self) -> bool

A flag to indicate whether the physical planner should valid the rule will not change the schema of the plan after the rewriting. Some of the optimization rules might change the nullable properties of the schema and should disable the schema check.