This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/datafusion-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 18ea5b1 Commit build products
18ea5b1 is described below
commit 18ea5b1505a860ffd87f75f1812b0a4ce61d5bb1
Author: Build Pelican (action) <[email protected]>
AuthorDate: Fri Aug 7 19:48:43 2026 +0000
Commit build products
---
blog/2026/08/07/datafusion-comet-1.0.0/index.html | 4 +---
blog/feeds/all-en.atom.xml | 4 +---
blog/feeds/blog.atom.xml | 4 +---
blog/feeds/pmc.atom.xml | 4 +---
4 files changed, 4 insertions(+), 12 deletions(-)
diff --git a/blog/2026/08/07/datafusion-comet-1.0.0/index.html
b/blog/2026/08/07/datafusion-comet-1.0.0/index.html
index 2a0325d..ca91107 100644
--- a/blog/2026/08/07/datafusion-comet-1.0.0/index.html
+++ b/blog/2026/08/07/datafusion-comet-1.0.0/index.html
@@ -153,9 +153,7 @@ running natively. Four consequences are worth calling
out.</p>
<p>The first is the biggest. An expression that opts into codegen dispatch
previously reached the dispatcher
only when Comet reported it as <em>incompatible</em> for the given input; an
<em>unsupported</em> report still sent the
whole subtree back to Spark. In 1.0 both support levels route through the
dispatcher, so an input that
-Spark handles and Comet's native code does not now stays inside the Comet
pipeline. This covers <code>concat</code>
-over non-string children, <code>sort_array</code> over nested arrays with
struct or null children, <code>array_intersect</code>
-over collated strings, and <code>trunc</code> / <code>date_trunc</code>
formats outside the native set.</p>
+Spark handles and Comet's native code does not now stays inside the Comet
pipeline.</p>
<p>Second, casts join the same path. Cast expressions that Comet declines to
run natively — including legacy
configuration variants such as
<code>spark.sql.legacy.castComplexTypesToString.enabled</code> — are now
dispatched
rather than falling back. More expressions were opted in as well:
<code>concat</code> under non-<code>UTF8_BINARY</code>
diff --git a/blog/feeds/all-en.atom.xml b/blog/feeds/all-en.atom.xml
index 5480347..41f4989 100644
--- a/blog/feeds/all-en.atom.xml
+++ b/blog/feeds/all-en.atom.xml
@@ -98,9 +98,7 @@ running natively. Four consequences are worth calling
out.</p>
<p>The first is the biggest. An expression that opts into codegen
dispatch previously reached the dispatcher
only when Comet reported it as <em>incompatible</em> for the given
input; an <em>unsupported</em> report still sent the
whole subtree back to Spark. In 1.0 both support levels route through the
dispatcher, so an input that
-Spark handles and Comet's native code does not now stays inside the Comet
pipeline. This covers <code>concat</code>
-over non-string children, <code>sort_array</code> over nested
arrays with struct or null children, <code>array_intersect</code>
-over collated strings, and <code>trunc</code> /
<code>date_trunc</code> formats outside the native set.</p>
+Spark handles and Comet's native code does not now stays inside the Comet
pipeline.</p>
<p>Second, casts join the same path. Cast expressions that Comet
declines to run natively — including legacy
configuration variants such as
<code>spark.sql.legacy.castComplexTypesToString.enabled</code> —
are now dispatched
rather than falling back. More expressions were opted in as well:
<code>concat</code> under non-<code>UTF8_BINARY</code>
diff --git a/blog/feeds/blog.atom.xml b/blog/feeds/blog.atom.xml
index da253ea..a4a4835 100644
--- a/blog/feeds/blog.atom.xml
+++ b/blog/feeds/blog.atom.xml
@@ -98,9 +98,7 @@ running natively. Four consequences are worth calling
out.</p>
<p>The first is the biggest. An expression that opts into codegen
dispatch previously reached the dispatcher
only when Comet reported it as <em>incompatible</em> for the given
input; an <em>unsupported</em> report still sent the
whole subtree back to Spark. In 1.0 both support levels route through the
dispatcher, so an input that
-Spark handles and Comet's native code does not now stays inside the Comet
pipeline. This covers <code>concat</code>
-over non-string children, <code>sort_array</code> over nested
arrays with struct or null children, <code>array_intersect</code>
-over collated strings, and <code>trunc</code> /
<code>date_trunc</code> formats outside the native set.</p>
+Spark handles and Comet's native code does not now stays inside the Comet
pipeline.</p>
<p>Second, casts join the same path. Cast expressions that Comet
declines to run natively — including legacy
configuration variants such as
<code>spark.sql.legacy.castComplexTypesToString.enabled</code> —
are now dispatched
rather than falling back. More expressions were opted in as well:
<code>concat</code> under non-<code>UTF8_BINARY</code>
diff --git a/blog/feeds/pmc.atom.xml b/blog/feeds/pmc.atom.xml
index 908d6f5..697e759 100644
--- a/blog/feeds/pmc.atom.xml
+++ b/blog/feeds/pmc.atom.xml
@@ -98,9 +98,7 @@ running natively. Four consequences are worth calling
out.</p>
<p>The first is the biggest. An expression that opts into codegen
dispatch previously reached the dispatcher
only when Comet reported it as <em>incompatible</em> for the given
input; an <em>unsupported</em> report still sent the
whole subtree back to Spark. In 1.0 both support levels route through the
dispatcher, so an input that
-Spark handles and Comet's native code does not now stays inside the Comet
pipeline. This covers <code>concat</code>
-over non-string children, <code>sort_array</code> over nested
arrays with struct or null children, <code>array_intersect</code>
-over collated strings, and <code>trunc</code> /
<code>date_trunc</code> formats outside the native set.</p>
+Spark handles and Comet's native code does not now stays inside the Comet
pipeline.</p>
<p>Second, casts join the same path. Cast expressions that Comet
declines to run natively — including legacy
configuration variants such as
<code>spark.sql.legacy.castComplexTypesToString.enabled</code> —
are now dispatched
rather than falling back. More expressions were opted in as well:
<code>concat</code> under non-<code>UTF8_BINARY</code>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
