Apache DataFusion SQL Query Engine
chore: Fix typos in comments (#22625)
Neil Conway2dcf0370f620
diff --git a/datafusion/physical-expr-adapter/src/schema_rewriter.rs b/datafusion/physical-expr-adapter/src/schema_rewriter.rsindex 9fb4950317..56502ab873 100644--- a/datafusion/physical-expr-adapter/src/schema_rewriter.rs+++ b/datafusion/physical-expr-adapter/src/schema_rewriter.rs@@ -432,7 +432,7 @@ impl DefaultPhysicalExprAdapterRewriter {// We need a cast expression whenever the logical and physical fields differ,// whether that difference is only metadata/nullability or also data type.// TODO: add optimization to move the cast from the column to literal expressions in the case of `col = 123`- // since that's much cheaper to evalaute.+ // since that's much cheaper to evaluate.// See https://github.com/apache/datafusion/issues/15780#issuecomment-2824716928validate_data_type_compatibility(resolved_column.name(),diff --git a/datafusion/physical-plan/src/aggregates/mod.rs b/datafusion/physical-plan/src/aggregates/mod.rsindex 541c27b5f2..c8b825d576 100644--- a/datafusion/physical-plan/src/aggregates/mod.rs+++ b/datafusion/physical-plan/src/aggregates/mod.rs@@ -550,7 +550,7 @@ impl From<StreamType> for SendableRecordBatchStream {/// The filter is kept in the `DataSourceExec`, and it will gets update during execution,/// the reader will interpret it as "the upstream only needs rows that such filter/// predicate is evaluated to true", and certain scanner implementation like `parquet`-/// can evalaute column statistics on those dynamic filters, to decide if they can+/// can evaluate column statistics on those dynamic filters, to decide if they can/// prune a whole range.////// ### Examples