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 aeb0e3a2ed Publish built docs triggered by
577c42458e8ab7a0869345678e7f0cd5dbf82771
aeb0e3a2ed is described below
commit aeb0e3a2ed51c196d5a32725de4c9a971463ae8f
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Mon May 19 19:51:37 2025 +0000
Publish built docs triggered by 577c42458e8ab7a0869345678e7f0cd5dbf82771
---
_sources/library-user-guide/upgrading.md.txt | 15 +++++++++++++++
library-user-guide/upgrading.html | 12 ++++++++++++
searchindex.js | 2 +-
3 files changed, 28 insertions(+), 1 deletion(-)
diff --git a/_sources/library-user-guide/upgrading.md.txt
b/_sources/library-user-guide/upgrading.md.txt
index bc6585c02f..415bb658d4 100644
--- a/_sources/library-user-guide/upgrading.md.txt
+++ b/_sources/library-user-guide/upgrading.md.txt
@@ -38,6 +38,21 @@ has been removed, so you will need to remove all references
to it.
`ScalarFunctionArgs` now contains a field called `arg_fields`. You can use this
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.
+
+The largest change to aggregate functions happens in the accumulator arguments.
+Both the `AccumulatorArgs` and `StateFieldsArgs` now contain `Field` rather
+than `DataType`.
+
+To upgrade window functions, `ExpressionArgs` now contains input fields instead
+of input data types. When setting these fields, the name of the field is
+not important since this gets overwritten during the planning stage. All you
+should need to do is wrap your existing data types in fields with nullability
+set depending on your use case.
+
### Physical Expression return `Field`
To support the changes to user defined functions processing metadata, the
diff --git a/library-user-guide/upgrading.html
b/library-user-guide/upgrading.html
index 6a5b74f598..03e5253f83 100644
--- a/library-user-guide/upgrading.html
+++ b/library-user-guide/upgrading.html
@@ -834,6 +834,18 @@ field is not important. It will be overwritten during
planning. <code class="doc
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
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>
+<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
+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
+not important since this gets overwritten during the planning stage. All you
+should need to do is wrap your existing data types in fields with nullability
+set depending on your use case.</p>
</section>
<section id="physical-expression-return-field">
<h3>Physical Expression return <code class="docutils literal
notranslate"><span class="pre">Field</span></code><a class="headerlink"
href="#physical-expression-return-field" title="Link to this heading">ΒΆ</a></h3>
diff --git a/searchindex.js b/searchindex.js
index 52633b7d30..c7952e58cb 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
