Struct datafusion_python::optimizer::eliminate_limit::EliminateLimit

pub struct EliminateLimit;

Optimizer rule to replace LIMIT 0 or LIMIT whose ancestor LIMIT’s skip is greater than or equal to current’s fetch

It can cooperate with propagate_empty_relation and limit_push_down. on a plan with an empty relation.

This rule also removes OFFSET 0 from the LogicalPlan

Implementations

impl EliminateLimit

pub fn new() -> EliminateLimit

Trait Implementations

impl Default for EliminateLimit

fn default() -> EliminateLimit

Returns the “default value” for a type.

impl OptimizerRule for EliminateLimit

fn name(&self) -> &str

A human readable name for this optimizer rule

fn apply_order(&self) -> Option<ApplyOrder>

How should the rule be applied by the optimizer? See comments on ApplyOrder for details.

fn supports_rewrite(&self) -> bool

Does this rule support rewriting owned plans (rather than by reference)?

fn rewrite( &self, plan: LogicalPlan, _config: &dyn OptimizerConfig, ) -> Result<Transformed<LogicalPlan>, DataFusionError>

Try to rewrite plan to an optimized form, returning Transformed::yes if the plan was rewritten and Transformed::no if it was not.

fn try_optimize( &self, _plan: &LogicalPlan, _config: &dyn OptimizerConfig, ) -> Result<Option<LogicalPlan>, DataFusionError>

👎Deprecated since 40.0.0: please implement supports_rewrite and rewrite instead

Try and rewrite plan to an optimized form, returning None if the plan cannot be optimized by this rule.