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 fc1fcc1640 Publish built docs triggered by
00132da33d51f272ddb19116121bed9a1420a0a5
fc1fcc1640 is described below
commit fc1fcc1640cf4999a7d5f1c15d129473ccff28cb
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed May 28 17:58:46 2025 +0000
Publish built docs triggered by 00132da33d51f272ddb19116121bed9a1420a0a5
---
_sources/library-user-guide/upgrading.md.txt | 8 ++++----
library-user-guide/upgrading.html | 14 +++++++-------
searchindex.js | 2 +-
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/_sources/library-user-guide/upgrading.md.txt
b/_sources/library-user-guide/upgrading.md.txt
index 2bf76e64ed..0c9c13a0ce 100644
--- a/_sources/library-user-guide/upgrading.md.txt
+++ b/_sources/library-user-guide/upgrading.md.txt
@@ -34,17 +34,17 @@ ListingOptions::new(Arc::new(ParquetFormat::default()))
// other options
```
-### Processing `Field` instead of `DataType` for user defined functions
+### Processing `FieldRef` instead of `DataType` for user defined functions
In order to support metadata handling and extension types, user defined
functions are
-now switching to traits which use `Field` rather than a `DataType` and
nullability.
+now switching to traits which use `FieldRef` rather than a `DataType` and
nullability.
This gives a single interface to both of these parameters and additionally
allows
access to metadata fields, which can be used for extension types.
To upgrade structs which implement `ScalarUDFImpl`, if you have implemented
`return_type_from_args` you need instead to implement `return_field_from_args`.
If your functions do not need to handle metadata, this should be
straightforward
-repackaging of the output data into a `Field`. The name you specify on the
+repackaging of the output data into a `FieldRef`. The name you specify on the
field is not important. It will be overwritten during planning. `ReturnInfo`
has been removed, so you will need to remove all references to it.
@@ -57,7 +57,7 @@ your function. You are not required to implement this if you
do not need to
handle metatdata.
The largest change to aggregate functions happens in the accumulator arguments.
-Both the `AccumulatorArgs` and `StateFieldsArgs` now contain `Field` rather
+Both the `AccumulatorArgs` and `StateFieldsArgs` now contain `FieldRef` rather
than `DataType`.
To upgrade window functions, `ExpressionArgs` now contains input fields instead
diff --git a/library-user-guide/upgrading.html
b/library-user-guide/upgrading.html
index c9644bf763..8262a4d8a7 100644
--- a/library-user-guide/upgrading.html
+++ b/library-user-guide/upgrading.html
@@ -565,11 +565,11 @@
</a>
</li>
<li class="toc-h3 nav-item toc-entry">
- <a class="reference internal nav-link"
href="#processing-field-instead-of-datatype-for-user-defined-functions">
+ <a class="reference internal nav-link"
href="#processing-fieldref-instead-of-datatype-for-user-defined-functions">
Processing
<code class="docutils literal notranslate">
<span class="pre">
- Field
+ FieldRef
</span>
</code>
instead of
@@ -859,16 +859,16 @@ explicitly set it to <code class="docutils literal
notranslate"><span class="pre
</pre></div>
</div>
</section>
-<section id="processing-field-instead-of-datatype-for-user-defined-functions">
-<h3>Processing <code class="docutils literal notranslate"><span
class="pre">Field</span></code> instead of <code class="docutils literal
notranslate"><span class="pre">DataType</span></code> for user defined
functions<a class="headerlink"
href="#processing-field-instead-of-datatype-for-user-defined-functions"
title="Link to this heading">¶</a></h3>
+<section
id="processing-fieldref-instead-of-datatype-for-user-defined-functions">
+<h3>Processing <code class="docutils literal notranslate"><span
class="pre">FieldRef</span></code> instead of <code class="docutils literal
notranslate"><span class="pre">DataType</span></code> for user defined
functions<a class="headerlink"
href="#processing-fieldref-instead-of-datatype-for-user-defined-functions"
title="Link to this heading">¶</a></h3>
<p>In order to support metadata handling and extension types, user defined
functions are
-now switching to traits which use <code class="docutils literal
notranslate"><span class="pre">Field</span></code> rather than a <code
class="docutils literal notranslate"><span class="pre">DataType</span></code>
and nullability.
+now switching to traits which use <code class="docutils literal
notranslate"><span class="pre">FieldRef</span></code> rather than a <code
class="docutils literal notranslate"><span class="pre">DataType</span></code>
and nullability.
This gives a single interface to both of these parameters and additionally
allows
access to metadata fields, which can be used for extension types.</p>
<p>To upgrade structs which implement <code class="docutils literal
notranslate"><span class="pre">ScalarUDFImpl</span></code>, if you have
implemented
<code class="docutils literal notranslate"><span
class="pre">return_type_from_args</span></code> you need instead to implement
<code class="docutils literal notranslate"><span
class="pre">return_field_from_args</span></code>.
If your functions do not need to handle metadata, this should be
straightforward
-repackaging of the output data into a <code class="docutils literal
notranslate"><span class="pre">Field</span></code>. The name you specify on the
+repackaging of the output data into a <code class="docutils literal
notranslate"><span class="pre">FieldRef</span></code>. The name you specify on
the
field is not important. It will be overwritten during planning. <code
class="docutils literal notranslate"><span class="pre">ReturnInfo</span></code>
has been removed, so you will need to remove all references to it.</p>
<p><code class="docutils literal notranslate"><span
class="pre">ScalarFunctionArgs</span></code> now contains a field called <code
class="docutils literal notranslate"><span
class="pre">arg_fields</span></code>. You can use this
@@ -878,7 +878,7 @@ to access the metadata associated with the columnar values
during invocation.</p
your function. You are not required to implement this if you do not need to
handle metatdata.</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">Field</span></code>
rather
+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>
<p>To upgrade window functions, <code class="docutils literal
notranslate"><span class="pre">ExpressionArgs</span></code> now contains input
fields instead
of input data types. When setting these fields, the name of the field is
diff --git a/searchindex.js b/searchindex.js
index ff8d40649b..507ba1ed18 100644
--- a/searchindex.js
+++ b/searchindex.js
@@ -1 +1 @@
-Search.setIndex({"alltitles":{"!=":[[54,"op-neq"]],"!~":[[54,"op-re-not-match"]],"!~*":[[54,"op-re-not-match-i"]],"!~~":[[54,"id19"]],"!~~*":[[54,"id20"]],"#":[[54,"op-bit-xor"]],"%":[[54,"op-modulo"]],"&":[[54,"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"]],"*":[[54,"op-multiply"]],"+":[[54,"op-plus"]],"-":[[54,"op-minus"]],"/":[[54,"op-divide"]],"2022
Q2":[[10,"q2"]] [...]
\ No newline at end of file
+Search.setIndex({"alltitles":{"!=":[[54,"op-neq"]],"!~":[[54,"op-re-not-match"]],"!~*":[[54,"op-re-not-match-i"]],"!~~":[[54,"id19"]],"!~~*":[[54,"id20"]],"#":[[54,"op-bit-xor"]],"%":[[54,"op-modulo"]],"&":[[54,"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"]],"*":[[54,"op-multiply"]],"+":[[54,"op-plus"]],"-":[[54,"op-minus"]],"/":[[54,"op-divide"]],"2022
Q2":[[10,"q2"]] [...]
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@datafusion.apache.org
For additional commands, e-mail: commits-h...@datafusion.apache.org
