Module datafusion::optimizer

re-export of datafusion_optimizer crate

Modules

• analyzer
• common_subexpr_eliminate
  Eliminate common sub-expression.
• decorrelate
• decorrelate_predicate_subquery
• eliminate_cross_join
  Optimizer rule to eliminate cross join to inner join if join predicates are available in filters.
• eliminate_duplicated_expr
• eliminate_filter
  Optimizer rule to replace where false on a plan with an empty relation. This saves time in planning and executing the query. Note that this rule should be applied after simplify expressions optimizer rule.
• eliminate_join
• eliminate_limit
  Optimizer rule to replace LIMIT 0 or LIMIT whose ancestor LIMIT's skip is greater than or equal to current's fetch on a plan with an empty relation. This rule also removes OFFSET 0 from the LogicalPlan This saves time in planning and executing the query.
• eliminate_outer_join
  Optimizer rule to eliminate left/right/full join to inner join if possible.
• eliminate_project
• extract_equijoin_predicate
  Optimizer rule to extract equijoin expr from filter
• filter_null_join_keys
  The FilterNullJoinKeys rule will identify inner joins with equi-join conditions where the join key is nullable on one side and non-nullable on the other side and then insert an IsNotNull filter on the nullable side since null values can never match.
• merge_projection
• optimizer
  Query optimizer traits
• propagate_empty_relation
• push_down_filter
  Push Down Filter optimizer rule ensures that filters are applied as early as possible in the plan
• push_down_limit
  Optimizer rule to push down LIMIT in the query plan It will push down through projection, limits (taking the smaller limit)
• push_down_projection
  Projection Push Down optimizer rule ensures that only referenced columns are loaded into memory
• replace_distinct_aggregate
• rewrite_disjunctive_predicate
• scalar_subquery_to_join
• simplify_expressions
• single_distinct_to_groupby
  single distinct to group by optimizer rule
• unwrap_cast_in_comparison
  Unwrap-cast binary comparison rule can be used to the binary/inlist comparison expr now, and other type of expr can be added if needed. This rule can reduce adding the Expr::Cast the expr instead of adding the Expr::Cast to literal expr.
• utils
  Collection of utility functions that are leveraged by the query optimizer rules

Macros

• generate_plan

Structs

• OptimizerContext
  A standalone OptimizerConfig that can be used independently of DataFusion’s config management

Traits

• OptimizerConfig
  Options to control the DataFusion Optimizer.
• OptimizerRule
  OptimizerRule transforms one LogicalPlan into another which computes the same results, but in a potentially more efficient way. If there are no suitable transformations for the input plan, the optimizer can simply return it as is.

Functions

• optimize_children
  Convenience rule for writing optimizers: recursively invoke optimize on plan’s children and then return a node of the same type. Useful for optimizer rules which want to leave the type of plan unchanged but still apply to the children. This also handles the case when the plan is a LogicalPlan::Explain.