This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/datafusion.git
The following commit(s) were added to refs/heads/asf-site by this push:
new bb33c212a4 Publish built docs triggered by
e0a05a693da6c56f97f001e0d5b3df1329b11ac2
bb33c212a4 is described below
commit bb33c212a480bcc0aeb1f8e8b2553d51aa3a7679
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Sat Aug 8 04:22:40 2026 +0000
Publish built docs triggered by e0a05a693da6c56f97f001e0d5b3df1329b11ac2
---
_sources/library-user-guide/building-logical-plans.md.txt | 2 +-
_sources/user-guide/explain-usage.md.txt | 4 ++--
library-user-guide/building-logical-plans.html | 2 +-
user-guide/explain-usage.html | 4 ++--
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/_sources/library-user-guide/building-logical-plans.md.txt
b/_sources/library-user-guide/building-logical-plans.md.txt
index 9dc0fcbf31..6efd97879a 100644
--- a/_sources/library-user-guide/building-logical-plans.md.txt
+++ b/_sources/library-user-guide/building-logical-plans.md.txt
@@ -86,7 +86,7 @@ Filter: person.id > Int32(500) [id:Int32;N, name:Utf8;N]
DataFusion logical plans can be created using the [LogicalPlanBuilder] struct.
There is also a [DataFrame] API which is
a higher-level API that delegates to [LogicalPlanBuilder].
-There are several functions that can can be used to create a new builder, such
as
+There are several functions that can be used to create a new builder, such as
- `empty` - create an empty plan with no fields
- `values` - create a plan from a set of literal values
diff --git a/_sources/user-guide/explain-usage.md.txt
b/_sources/user-guide/explain-usage.md.txt
index 40ff369b58..bc9dace297 100644
--- a/_sources/user-guide/explain-usage.md.txt
+++ b/_sources/user-guide/explain-usage.md.txt
@@ -169,7 +169,7 @@ debugging to see why and when DataFusion added and removed
operators from a plan
During execution, DataFusion operators collect detailed metrics. You can access
them programmatically via [`ExecutionPlan::metrics`] as well as with the
-`EXPLAIN ANALYZE` command. For example here is the same query query as
+`EXPLAIN ANALYZE` command. For example here is the same query as
above but with `EXPLAIN ANALYZE` (note the output is edited for clarity)
[`executionplan::metrics`]:
https://docs.rs/datafusion/latest/datafusion/physical_plan/trait.ExecutionPlan.html#method.metrics
@@ -365,7 +365,7 @@ For this query, let's again read the plan from the bottom
to the top:
- `gby=[UserID@0 as UserID]`: Represents `GROUP BY` in the [physical plan]
and groups together the same values of `UserID`.
- `aggr=[count(*)]`: Applies the `COUNT` aggregate on all rows for each
group.
- `RepartitionExec`
- - `partitioning=Hash([UserID@0], 10)`: Divides the input into into 10 (new)
output partitions based on the value of `hash(UserID)`. You can read more about
this in the [partitioning] documentation.
+ - `partitioning=Hash([UserID@0], 10)`: Divides the input into 10 (new)
output partitions based on the value of `hash(UserID)`. You can read more about
this in the [partitioning] documentation.
- `input_partitions=10`: Number of input partitions.
- `CoalesceBatchesExec`
- `target_batch_size=8192`: Combines smaller batches in to larger batches.
In this case approximately 8192 rows in each batch.
diff --git a/library-user-guide/building-logical-plans.html
b/library-user-guide/building-logical-plans.html
index 52d05e5e1a..5a5c0063a1 100644
--- a/library-user-guide/building-logical-plans.html
+++ b/library-user-guide/building-logical-plans.html
@@ -502,7 +502,7 @@ much easier to use the <a class="reference external"
href="https://docs.rs/dataf
<h2>Building Logical Plans with LogicalPlanBuilder<a class="headerlink"
href="#building-logical-plans-with-logicalplanbuilder" title="Link to this
heading">#</a></h2>
<p>DataFusion logical plans can be created using the <a class="reference
external"
href="https://docs.rs/datafusion-expr/latest/datafusion_expr/logical_plan/builder/struct.LogicalPlanBuilder.html";>LogicalPlanBuilder</a>
struct. There is also a <a class="reference internal"
href="using-the-dataframe-api.html"><span class="std
std-doc">DataFrame</span></a> API which is
a higher-level API that delegates to <a class="reference external"
href="https://docs.rs/datafusion-expr/latest/datafusion_expr/logical_plan/builder/struct.LogicalPlanBuilder.html";>LogicalPlanBuilder</a>.</p>
-<p>There are several functions that can can be used to create a new builder,
such as</p>
+<p>There are several functions that can be used to create a new builder, such
as</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span
class="pre">empty</span></code> - create an empty plan with no fields</p></li>
<li><p><code class="docutils literal notranslate"><span
class="pre">values</span></code> - create a plan from a set of literal
values</p></li>
diff --git a/user-guide/explain-usage.html b/user-guide/explain-usage.html
index 7e57fa77da..bbb72a1303 100644
--- a/user-guide/explain-usage.html
+++ b/user-guide/explain-usage.html
@@ -583,7 +583,7 @@ debugging to see why and when DataFusion added and removed
operators from a plan
<h2>Execution Counters: <code class="docutils literal notranslate"><span
class="pre">EXPLAIN</span> <span class="pre">ANALYZE</span></code><a
class="headerlink" href="#execution-counters-explain-analyze" title="Link to
this heading">#</a></h2>
<p>During execution, DataFusion operators collect detailed metrics. You can
access
them programmatically via <a class="reference external"
href="https://docs.rs/datafusion/latest/datafusion/physical_plan/trait.ExecutionPlan.html#method.metrics";><code
class="docutils literal notranslate"><span
class="pre">ExecutionPlan::metrics</span></code></a> as well as with the
-<code class="docutils literal notranslate"><span class="pre">EXPLAIN</span>
<span class="pre">ANALYZE</span></code> command. For example here is the same
query query as
+<code class="docutils literal notranslate"><span class="pre">EXPLAIN</span>
<span class="pre">ANALYZE</span></code> command. For example here is the same
query as
above but with <code class="docutils literal notranslate"><span
class="pre">EXPLAIN</span> <span class="pre">ANALYZE</span></code> (note the
output is edited for clarity)</p>
<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span class="o">></span><span class="w">
</span><span class="k">EXPLAIN</span><span class="w"> </span><span
class="k">ANALYZE</span><span class="w"> </span><span
class="k">SELECT</span><span class="w"> </span><span
class="ss">"WatchID"</span><span class="w"> </span><span
class="k">AS</span><span class="w"> </span><span class="n">wid</span><span
class="p">,</span><span class="w"> </span><span clas [...]
<span class="k">FROM</span><span class="w"> </span><span
class="s1">'hits.parquet'</span>
@@ -827,7 +827,7 @@ number of hits:</p>
</li>
<li><p><code class="docutils literal notranslate"><span
class="pre">RepartitionExec</span></code></p>
<ul>
-<li><p><code class="docutils literal notranslate"><span
class="pre">partitioning=Hash([UserID@0],</span> <span
class="pre">10)</span></code>: Divides the input into into 10 (new) output
partitions based on the value of <code class="docutils literal
notranslate"><span class="pre">hash(UserID)</span></code>. You can read more
about this in the <a class="reference external"
href="https://docs.rs/datafusion/latest/datafusion/physical_plan/repartition/struct.RepartitionExec.html";>partitio
[...]
+<li><p><code class="docutils literal notranslate"><span
class="pre">partitioning=Hash([UserID@0],</span> <span
class="pre">10)</span></code>: Divides the input into 10 (new) output
partitions based on the value of <code class="docutils literal
notranslate"><span class="pre">hash(UserID)</span></code>. You can read more
about this in the <a class="reference external"
href="https://docs.rs/datafusion/latest/datafusion/physical_plan/repartition/struct.RepartitionExec.html";>partitioning<
[...]
<li><p><code class="docutils literal notranslate"><span
class="pre">input_partitions=10</span></code>: Number of input
partitions.</p></li>
</ul>
</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
