Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456
datafusion::physical_plan::execution_plan - Rust
[go: Go Back, main page]

datafusion::physical_plan

Module execution_plan

source

Modules§

  • Defines physical expressions that can evaluated at runtime during query execution
  • Deprecated module. Add new feature in scalar_function.rs
  • Functionality used both on logical and physical plans

Macros§

Structs§

  • Statistics for a column within a relation
  • A newtype wrapper to display T implementingDisplayAs using the Default mode
  • EmptyRecordBatchStream can be used to create a RecordBatchStream that will produce no results
  • Something that tracks a value of interest (metric) of a DataFusion ExecutionPlan execution.
  • Stores certain, often expensive to compute, plan properties used in query optimization.
  • Statistics for a relation Fields are optional and can be inexact because the sources sometimes provide approximate estimates for performance reasons and the transformations output are not always predictable.
  • A newtype wrapper to display T implementing DisplayAs using the Verbose mode

Enums§

Traits§

Functions§

  • Checks a RecordBatch for not null constraints on specified columns.
  • Execute the ExecutionPlan and collect the results in memory
  • Execute the ExecutionPlan and collect the results in memory
  • Return a wrapper around an ExecutionPlan which can be displayed in various easier to understand ways.
  • Executes an input stream and ensures that the resulting stream adheres to the not null constraints specified in the sink_schema.
  • Execute the ExecutionPlan and return a single stream of RecordBatches.
  • Execute the ExecutionPlan and return a vec with one stream per output partition
  • Utility function yielding a string representation of the given ExecutionPlan.
  • Indicate whether a data exchange is needed for the input of plan, which will be very helpful especially for the distributed engine to judge whether need to deal with shuffling. Currently there are 3 kinds of execution plan which needs data exchange 1. RepartitionExec for changing the partition number between two ExecutionPlans 2. CoalescePartitionsExec for collapsing all of the partitions into one without ordering guarantee 3. SortPreservingMergeExec for collapsing all of the sorted partitions into one with ordering guarantee
  • Applies an optional projection to a SchemaRef, returning the projected schema
  • Returns a copy of this plan if we change any child according to the pointer comparison. The size of children must be equal to the size of ExecutionPlan::children().

Type Aliases§