This is an automated email from the ASF dual-hosted git repository.
github-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 65c98e3b71 Publish built docs triggered by
1c86ec7f5244c3b2e6d3ac722640ef678a027a18
65c98e3b71 is described below
commit 65c98e3b719fc9ca3cdb16738f98fa1daf9e2102
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed Aug 27 21:15:17 2025 +0000
Publish built docs triggered by 1c86ec7f5244c3b2e6d3ac722640ef678a027a18
---
_sources/library-user-guide/extending-operators.md.txt | 2 +-
_sources/library-user-guide/upgrading.md.txt | 8 ++++----
_sources/user-guide/configs.md.txt | 2 +-
_sources/user-guide/explain-usage.md.txt | 2 +-
library-user-guide/extending-operators.html | 2 +-
library-user-guide/upgrading.html | 8 ++++----
searchindex.js | 2 +-
user-guide/configs.html | 2 +-
user-guide/explain-usage.html | 2 +-
9 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/_sources/library-user-guide/extending-operators.md.txt
b/_sources/library-user-guide/extending-operators.md.txt
index 7a5f888848..c7b9cb2b10 100644
--- a/_sources/library-user-guide/extending-operators.md.txt
+++ b/_sources/library-user-guide/extending-operators.md.txt
@@ -36,7 +36,7 @@ fn rewrite(
plan: LogicalPlan,
_config: &dyn OptimizerConfig,
) -> Result<Transformed<LogicalPlan>> {
- // Attemps to rewrite a logical plan to a uwheel-based plan that either
provides
+ // Attempts to rewrite a logical plan to a uwheel-based plan that either
provides
// plan-time aggregates or skips execution based on min/max pruning.
if let Some(rewritten) = self.try_rewrite(&plan) {
Ok(Transformed::yes(rewritten))
diff --git a/_sources/library-user-guide/upgrading.md.txt
b/_sources/library-user-guide/upgrading.md.txt
index 7a3156d3bf..2d76b9d6b4 100644
--- a/_sources/library-user-guide/upgrading.md.txt
+++ b/_sources/library-user-guide/upgrading.md.txt
@@ -168,7 +168,7 @@ for more details.
### Added `ExecutionPlan::reset_state`
-In order to fix a bug in DataFusion `49.0.0` where dynamic filters (currently
only generated in the precense of a query such as `ORDER BY ... LIMIT ...`)
+In order to fix a bug in DataFusion `49.0.0` where dynamic filters (currently
only generated in the presence of a query such as `ORDER BY ... LIMIT ...`)
produced incorrect results in recursive queries, a new method `reset_state`
has been added to the `ExecutionPlan` trait.
Any `ExecutionPlan` that needs to maintain internal state or references to
other nodes in the execution plan tree should implement this method to reset
that state.
@@ -572,7 +572,7 @@ to access the metadata associated with the columnar values
during invocation.
To upgrade user defined aggregate functions, there is now a function
`return_field` that will allow you to specify both metadata and nullability of
your function. You are not required to implement this if you do not need to
-handle metatdata.
+handle metadata.
The largest change to aggregate functions happens in the accumulator arguments.
Both the `AccumulatorArgs` and `StateFieldsArgs` now contain `FieldRef` rather
@@ -912,8 +912,8 @@ Elapsed 0.005 seconds.
DataFusion 46 has changed the way scalar array function signatures are
declared. Previously, functions needed to select from a list of predefined
signatures within the `ArrayFunctionSignature` enum. Now the signatures
-can be defined via a `Vec` of psuedo-types, which each correspond to a
-single argument. Those psuedo-types are the variants of the
+can be defined via a `Vec` of pseudo-types, which each correspond to a
+single argument. Those pseudo-types are the variants of the
`ArrayFunctionArgument` enum and are as follows:
- `Array`: An argument of type List/LargeList/FixedSizeList. All Array
diff --git a/_sources/user-guide/configs.md.txt
b/_sources/user-guide/configs.md.txt
index 0736376fa8..877a46ef47 100644
--- a/_sources/user-guide/configs.md.txt
+++ b/_sources/user-guide/configs.md.txt
@@ -239,7 +239,7 @@ In conclusion, for queries under a very tight memory limit,
it's recommended to
set `target_partitions` and `batch_size` to smaller values.
```sql
--- Query still gets paralleized, but each partition will have more memory to
use
+-- Query still gets parallelized, but each partition will have more memory to
use
SET datafusion.execution.target_partitions = 4;
-- Smaller than the default '8192', while still keep the benefit of vectorized
execution
SET datafusion.execution.batch_size = 1024;
diff --git a/_sources/user-guide/explain-usage.md.txt
b/_sources/user-guide/explain-usage.md.txt
index 68712012f4..2289205089 100644
--- a/_sources/user-guide/explain-usage.md.txt
+++ b/_sources/user-guide/explain-usage.md.txt
@@ -249,7 +249,7 @@ a separate core. Data crosses between cores only within
certain operators such a
You can read more about this in the [Partitioning Docs].
-[partitoning docs]:
https://docs.rs/datafusion/latest/datafusion/physical_expr/enum.Partitioning.html
+[partitioning docs]:
https://docs.rs/datafusion/latest/datafusion/physical_expr/enum.Partitioning.html
## Example of an Aggregate Query
diff --git a/library-user-guide/extending-operators.html
b/library-user-guide/extending-operators.html
index 81a9ac9365..714c7a1398 100644
--- a/library-user-guide/extending-operators.html
+++ b/library-user-guide/extending-operators.html
@@ -622,7 +622,7 @@
<span class="w"> </span><span class="n">plan</span><span
class="p">:</span><span class="w"> </span><span
class="nc">LogicalPlan</span><span class="p">,</span>
<span class="w"> </span><span class="n">_config</span><span
class="p">:</span><span class="w"> </span><span class="kp">&</span><span
class="nc">dyn</span><span class="w"> </span><span
class="n">OptimizerConfig</span><span class="p">,</span>
<span class="p">)</span><span class="w"> </span><span
class="p">-></span><span class="w"> </span><span
class="nb">Result</span><span class="o"><</span><span
class="n">Transformed</span><span class="o"><</span><span
class="n">LogicalPlan</span><span class="o">>></span><span class="w">
</span><span class="p">{</span>
-<span class="w"> </span><span class="c1">// Attemps to rewrite a logical
plan to a uwheel-based plan that either provides</span>
+<span class="w"> </span><span class="c1">// Attempts to rewrite a logical
plan to a uwheel-based plan that either provides</span>
<span class="w"> </span><span class="c1">// plan-time aggregates or skips
execution based on min/max pruning.</span>
<span class="w"> </span><span class="k">if</span><span class="w">
</span><span class="kd">let</span><span class="w"> </span><span
class="nb">Some</span><span class="p">(</span><span
class="n">rewritten</span><span class="p">)</span><span class="w"> </span><span
class="o">=</span><span class="w"> </span><span class="bp">self</span><span
class="p">.</span><span class="n">try_rewrite</span><span
class="p">(</span><span class="o">&</span><span class="n">plan</span><span
class="p">)</s [...]
<span class="w"> </span><span class="nb">Ok</span><span
class="p">(</span><span class="n">Transformed</span><span
class="p">::</span><span class="n">yes</span><span class="p">(</span><span
class="n">rewritten</span><span class="p">))</span>
diff --git a/library-user-guide/upgrading.html
b/library-user-guide/upgrading.html
index 90117adf1b..3547c469c5 100644
--- a/library-user-guide/upgrading.html
+++ b/library-user-guide/upgrading.html
@@ -1359,7 +1359,7 @@ for more details.</p>
</section>
<section id="added-executionplan-reset-state">
<h3>Added <code class="docutils literal notranslate"><span
class="pre">ExecutionPlan::reset_state</span></code><a class="headerlink"
href="#added-executionplan-reset-state" title="Link to this heading">¶</a></h3>
-<p>In order to fix a bug in DataFusion <code class="docutils literal
notranslate"><span class="pre">49.0.0</span></code> where dynamic filters
(currently only generated in the precense of a query such as <code
class="docutils literal notranslate"><span class="pre">ORDER</span> <span
class="pre">BY</span> <span class="pre">...</span> <span
class="pre">LIMIT</span> <span class="pre">...</span></code>)
+<p>In order to fix a bug in DataFusion <code class="docutils literal
notranslate"><span class="pre">49.0.0</span></code> where dynamic filters
(currently only generated in the presence of a query such as <code
class="docutils literal notranslate"><span class="pre">ORDER</span> <span
class="pre">BY</span> <span class="pre">...</span> <span
class="pre">LIMIT</span> <span class="pre">...</span></code>)
produced incorrect results in recursive queries, a new method <code
class="docutils literal notranslate"><span
class="pre">reset_state</span></code> has been added to the <code
class="docutils literal notranslate"><span
class="pre">ExecutionPlan</span></code> trait.</p>
<p>Any <code class="docutils literal notranslate"><span
class="pre">ExecutionPlan</span></code> that needs to maintain internal state
or references to other nodes in the execution plan tree should implement this
method to reset that state.
See <a class="reference external"
href="https://github.com/apache/datafusion/pull/17028";>#17028</a> for more
details and an example implementation for <code class="docutils literal
notranslate"><span class="pre">SortExec</span></code>.</p>
@@ -1695,7 +1695,7 @@ to access the metadata associated with the columnar
values during invocation.</p
<p>To upgrade user defined aggregate functions, there is now a function
<code class="docutils literal notranslate"><span
class="pre">return_field</span></code> that will allow you to specify both
metadata and nullability of
your function. You are not required to implement this if you do not need to
-handle metatdata.</p>
+handle metadata.</p>
<p>The largest change to aggregate functions happens in the accumulator
arguments.
Both the <code class="docutils literal notranslate"><span
class="pre">AccumulatorArgs</span></code> and <code class="docutils literal
notranslate"><span class="pre">StateFieldsArgs</span></code> now contain <code
class="docutils literal notranslate"><span class="pre">FieldRef</span></code>
rather
than <code class="docutils literal notranslate"><span
class="pre">DataType</span></code>.</p>
@@ -1978,8 +1978,8 @@ the following must be changed:</p>
<p>DataFusion 46 has changed the way scalar array function signatures are
declared. Previously, functions needed to select from a list of predefined
signatures within the <code class="docutils literal notranslate"><span
class="pre">ArrayFunctionSignature</span></code> enum. Now the signatures
-can be defined via a <code class="docutils literal notranslate"><span
class="pre">Vec</span></code> of psuedo-types, which each correspond to a
-single argument. Those psuedo-types are the variants of the
+can be defined via a <code class="docutils literal notranslate"><span
class="pre">Vec</span></code> of pseudo-types, which each correspond to a
+single argument. Those pseudo-types are the variants of the
<code class="docutils literal notranslate"><span
class="pre">ArrayFunctionArgument</span></code> enum and are as follows:</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span
class="pre">Array</span></code>: An argument of type
List/LargeList/FixedSizeList. All Array
diff --git a/searchindex.js b/searchindex.js
index c1c0af4d73..90cd7c7031 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles":{"!=":[[57,"op-neq"]],"!~":[[57,"op-re-not-match"]],"!~*":[[57,"op-re-not-match-i"]],"!~~":[[57,"id19"]],"!~~*":[[57,"id20"]],"#":[[57,"op-bit-xor"]],"%":[[57,"op-modulo"]],"&":[[57,"op-bit-and"]],"(relation,
name) tuples in logical fields and logical columns are
unique":[[12,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[57,"op-multiply"]],"+":[[57,"op-plus"]],"-":[[57,"op-minus"]],"/":[[57,"op-divide"]],"<":[[57,"op-lt"]],"<
[...]
\ No newline at end of file
+Search.setIndex({"alltitles":{"!=":[[57,"op-neq"]],"!~":[[57,"op-re-not-match"]],"!~*":[[57,"op-re-not-match-i"]],"!~~":[[57,"id19"]],"!~~*":[[57,"id20"]],"#":[[57,"op-bit-xor"]],"%":[[57,"op-modulo"]],"&":[[57,"op-bit-and"]],"(relation,
name) tuples in logical fields and logical columns are
unique":[[12,"relation-name-tuples-in-logical-fields-and-logical-columns-are-unique"]],"*":[[57,"op-multiply"]],"+":[[57,"op-plus"]],"-":[[57,"op-minus"]],"/":[[57,"op-divide"]],"<":[[57,"op-lt"]],"<
[...]
\ No newline at end of file
diff --git a/user-guide/configs.html b/user-guide/configs.html
index d01f940f5c..ea3d0dbbee 100644
--- a/user-guide/configs.html
+++ b/user-guide/configs.html
@@ -1195,7 +1195,7 @@ The larger this value, the fewer spilled sorted runs can
be merged. Decreasing t
can help reduce the number of subsequent spills required.</p>
<p>In conclusion, for queries under a very tight memory limit, it’s
recommended to
set <code class="docutils literal notranslate"><span
class="pre">target_partitions</span></code> and <code class="docutils literal
notranslate"><span class="pre">batch_size</span></code> to smaller values.</p>
-<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span class="c1">-- Query still gets
paralleized, but each partition will have more memory to use</span>
+<div class="highlight-sql notranslate"><div
class="highlight"><pre><span></span><span class="c1">-- Query still gets
parallelized, but each partition will have more memory to use</span>
<span class="k">SET</span><span class="w"> </span><span
class="n">datafusion</span><span class="p">.</span><span
class="n">execution</span><span class="p">.</span><span
class="n">target_partitions</span><span class="w"> </span><span
class="o">=</span><span class="w"> </span><span class="mi">4</span><span
class="p">;</span>
<span class="c1">-- Smaller than the default '8192', while still keep
the benefit of vectorized execution</span>
<span class="k">SET</span><span class="w"> </span><span
class="n">datafusion</span><span class="p">.</span><span
class="n">execution</span><span class="p">.</span><span
class="n">batch_size</span><span class="w"> </span><span
class="o">=</span><span class="w"> </span><span class="mi">1024</span><span
class="p">;</span>
diff --git a/user-guide/explain-usage.html b/user-guide/explain-usage.html
index bd60532916..da30a3b0e3 100644
--- a/user-guide/explain-usage.html
+++ b/user-guide/explain-usage.html
@@ -890,7 +890,7 @@ by all 16 cores.</p>
planning. Roughly speaking, each “partition” in the plan is run independently
using
a separate core. Data crosses between cores only within certain operators such
as
<code class="docutils literal notranslate"><span
class="pre">RepartitionExec</span></code>, <code class="docutils literal
notranslate"><span class="pre">CoalescePartitions</span></code> and <code
class="docutils literal notranslate"><span
class="pre">SortPreservingMergeExec</span></code></p>
-<p>You can read more about this in the [Partitioning Docs].</p>
+<p>You can read more about this in the <a class="reference external"
href="https://docs.rs/datafusion/latest/datafusion/physical_expr/enum.Partitioning.html";>Partitioning
Docs</a>.</p>
</section>
<section id="example-of-an-aggregate-query">
<h2>Example of an Aggregate Query<a class="headerlink"
href="#example-of-an-aggregate-query" title="Link to this heading">¶</a></h2>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@datafusion.apache.org
For additional commands, e-mail: commits-h...@datafusion.apache.org
