Struct PushCsrTargetFilters 

pub struct PushCsrTargetFilters;

Optimizer rule: move WHERE conjuncts that read only a fused target’s columns into the CSR node, which evaluates them before taking the target’s other columns.

Without this, ... WHERE tc.name = 'Athlete' takes every projected target column for every expanded row, then filters. The CSR node instead takes just the filter’s columns for each batch’s candidates, evaluates the predicate, and takes the remaining columns only for rows that pass; columns used only by the filter are then pruned from the output. The cost follows the expanded rows, never the target table’s size. (Evaluating the filter once per query over the whole target table was tried first: it cost more than it saved whenever the expansion was already small, which re-rooting usually ensures.) Volatile conjuncts stay put.

Trait Implementations

impl Debug for PushCsrTargetFilters

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

Formats the value using the given formatter.

impl Default for PushCsrTargetFilters

fn default() -> Self

Returns the “default value” for a type.

impl OptimizerRule for PushCsrTargetFilters

fn name(&self) -> &str

A human readable name for this optimizer rule

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

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

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

👎Deprecated since 47.0.0:

This method is no longer used

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