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 1c81894425 Publish built docs triggered by
b4a8b5ae54d939353b7cbd5ab8aee7d3bedecb66
1c81894425 is described below
commit 1c818944259b29091c08e9bed7f37f6ba9294ed4
Author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AuthorDate: Fri Sep 5 15:04:35 2025 +0000
Publish built docs triggered by b4a8b5ae54d939353b7cbd5ab8aee7d3bedecb66
---
_sources/library-user-guide/upgrading.md.txt | 19 +++++++++++++++++++
library-user-guide/upgrading.html | 24 ++++++++++++++++++++++++
searchindex.js | 2 +-
3 files changed, 44 insertions(+), 1 deletion(-)
diff --git a/_sources/library-user-guide/upgrading.md.txt
b/_sources/library-user-guide/upgrading.md.txt
index e27408e48c..8c26d4e9a9 100644
--- a/_sources/library-user-guide/upgrading.md.txt
+++ b/_sources/library-user-guide/upgrading.md.txt
@@ -275,6 +275,25 @@ If you have custom implementations of `FileOpener` or work
directly with `FileOp
[#17397]: https://github.com/apache/datafusion/pull/17397
+### Added `PhysicalExpr::is_volatile_node`
+
+We added a method to `PhysicalExpr` to mark a `PhysicalExpr` as volatile:
+
+```rust
+,ignore
+impl PhysicalExpr for MyRandomExpr {
+ fn is_volatile_node(&self) -> bool {
+ true
+ }
+}
+```
+
+We've shipped this with a default value of `false` to minimize breakage but we
highly recommend that implementers of `PhysicalExpr` opt into a behavior, even
if it is returning `false`.
+
+You can see more discussion and example implementations in [#17351].
+
+[#17351]: https://github.com/apache/datafusion/pull/17351
+
## DataFusion `49.0.0`
### `MSRV` updated to 1.85.1
diff --git a/library-user-guide/upgrading.html
b/library-user-guide/upgrading.html
index 8f24327a9f..8360749a8c 100644
--- a/library-user-guide/upgrading.html
+++ b/library-user-guide/upgrading.html
@@ -760,6 +760,16 @@
</code>
</a>
</li>
+ <li class="toc-h3 nav-item toc-entry">
+ <a class="reference internal nav-link"
href="#added-physicalexpr-is-volatile-node">
+ Added
+ <code class="docutils literal notranslate">
+ <span class="pre">
+ PhysicalExpr::is_volatile_node
+ </span>
+ </code>
+ </a>
+ </li>
</ul>
</li>
<li class="toc-h2 nav-item toc-entry">
@@ -1486,6 +1496,20 @@ Reimplementation for any custom <code class="docutils
literal notranslate"><span
</div>
<p>If you have custom implementations of <code class="docutils literal
notranslate"><span class="pre">FileOpener</span></code> or work directly with
<code class="docutils literal notranslate"><span
class="pre">FileOpenFuture</span></code>, you’ll need to update your error
handling to use <code class="docutils literal notranslate"><span
class="pre">DataFusionError</span></code> instead of <code class="docutils
literal notranslate"><span class="pre">ArrowError</span></code>. The <code clas
[...]
</section>
+<section id="added-physicalexpr-is-volatile-node">
+<h3>Added <code class="docutils literal notranslate"><span
class="pre">PhysicalExpr::is_volatile_node</span></code><a class="headerlink"
href="#added-physicalexpr-is-volatile-node" title="Link to this
heading">¶</a></h3>
+<p>We added a method to <code class="docutils literal notranslate"><span
class="pre">PhysicalExpr</span></code> to mark a <code class="docutils literal
notranslate"><span class="pre">PhysicalExpr</span></code> as volatile:</p>
+<div class="highlight-rust notranslate"><div
class="highlight"><pre><span></span><span class="p">,</span><span
class="n">ignore</span>
+<span class="k">impl</span><span class="w"> </span><span
class="n">PhysicalExpr</span><span class="w"> </span><span
class="k">for</span><span class="w"> </span><span
class="n">MyRandomExpr</span><span class="w"> </span><span class="p">{</span>
+<span class="w"> </span><span class="k">fn</span><span class="w">
</span><span class="nf">is_volatile_node</span><span class="p">(</span><span
class="o">&</span><span class="bp">self</span><span class="p">)</span><span
class="w"> </span><span class="p">-></span><span class="w"> </span><span
class="kt">bool</span><span class="w"> </span><span class="p">{</span>
+<span class="w"> </span><span class="kc">true</span>
+<span class="w"> </span><span class="p">}</span>
+<span class="p">}</span>
+</pre></div>
+</div>
+<p>We’ve shipped this with a default value of <code class="docutils literal
notranslate"><span class="pre">false</span></code> to minimize breakage but we
highly recommend that implementers of <code class="docutils literal
notranslate"><span class="pre">PhysicalExpr</span></code> opt into a behavior,
even if it is returning <code class="docutils literal notranslate"><span
class="pre">false</span></code>.</p>
+<p>You can see more discussion and example implementations in <a
class="reference external"
href="https://github.com/apache/datafusion/pull/17351";>#17351</a>.</p>
+</section>
</section>
<section id="datafusion-49-0-0">
<h2>DataFusion <code class="docutils literal notranslate"><span
class="pre">49.0.0</span></code><a class="headerlink" href="#datafusion-49-0-0"
title="Link to this heading">¶</a></h2>
diff --git a/searchindex.js b/searchindex.js
index e736210b9e..15640d019c 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
