This is an automated email from the ASF dual-hosted git repository.
wayne pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-datafusion.git
The following commit(s) were added to refs/heads/main by this push:
new 7889bf9c4f Fix typo in partitioning.rs (#8134)
7889bf9c4f is described below
commit 7889bf9c4f171b6319ef57b5d17ca8aeea64fa68
Author: 张林伟 <[email protected]>
AuthorDate: Mon Nov 13 16:54:24 2023 +0800
Fix typo in partitioning.rs (#8134)
* Fix typo in partitioning.rs
* Update partitioning.rs
---
datafusion/physical-expr/src/partitioning.rs | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/datafusion/physical-expr/src/partitioning.rs
b/datafusion/physical-expr/src/partitioning.rs
index cbacb7a8a9..301f12e9aa 100644
--- a/datafusion/physical-expr/src/partitioning.rs
+++ b/datafusion/physical-expr/src/partitioning.rs
@@ -26,7 +26,7 @@ use crate::{physical_exprs_equal, EquivalenceProperties,
PhysicalExpr};
///
/// When `executed`, `ExecutionPlan`s produce one or more independent stream
of
/// data batches in parallel, referred to as partitions. The streams are Rust
-/// `aync` [`Stream`]s (a special kind of future). The number of output
+/// `async` [`Stream`]s (a special kind of future). The number of output
/// partitions varies based on the input and the operation performed.
///
/// For example, an `ExecutionPlan` that has output partitioning of 3 will
@@ -64,7 +64,7 @@ use crate::{physical_exprs_equal, EquivalenceProperties,
PhysicalExpr};
/// ```
///
/// It is common (but not required) that an `ExecutionPlan` has the same number
-/// of input partitions as output partitons. However, some plans have different
+/// of input partitions as output partitions. However, some plans have
different
/// numbers such as the `RepartitionExec` that redistributes batches from some
/// number of inputs to some number of outputs
///
