You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@datafusion.apache.org by gi...@apache.org on 2026/05/29 15:29:03 UTC
(datafusion) branch gh-readonly-queue/main/pr-22625-22f4bc20ef388f89c1cf6a5aa85f06f46225dfc1 created (now 2dcf0370f6)
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a change to branch gh-readonly-queue/main/pr-22625-22f4bc20ef388f89c1cf6a5aa85f06f46225dfc1
in repository https://gitbox.apache.org/repos/asf/datafusion.git
at 2dcf0370f6 chore: Fix typos in comments (#22625)
This branch includes the following new commits:
new 2dcf0370f6 chore: Fix typos in comments (#22625)
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datafusion.apache.org
For additional commands, e-mail: commits-help@datafusion.apache.org
(datafusion) 01/01: chore: Fix typos in comments (#22625)
Posted by gi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/main/pr-22625-22f4bc20ef388f89c1cf6a5aa85f06f46225dfc1
in repository https://gitbox.apache.org/repos/asf/datafusion.git
commit 2dcf0370f6207a8c7aa097ba2d9d7c2b58a6806b
Author: Neil Conway <ne...@gmail.com>
AuthorDate: Fri May 29 11:28:39 2026 -0400
chore: Fix typos in comments (#22625)
## Which issue does this PR close?
N/A
## Rationale for this change
Upgraded `typos` catches two more typos.
## What changes are included in this PR?
Fix typos.
## Are these changes tested?
No functional change.
## Are there any user-facing changes?
No.
---
datafusion/physical-expr-adapter/src/schema_rewriter.rs | 2 +-
datafusion/physical-plan/src/aggregates/mod.rs | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/datafusion/physical-expr-adapter/src/schema_rewriter.rs b/datafusion/physical-expr-adapter/src/schema_rewriter.rs
index 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-2824716928
validate_data_type_compatibility(
resolved_column.name(),
diff --git a/datafusion/physical-plan/src/aggregates/mod.rs b/datafusion/physical-plan/src/aggregates/mod.rs
index 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
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datafusion.apache.org
For additional commands, e-mail: commits-help@datafusion.apache.org