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 7364986 Commit build products
7364986 is described below
commit 73649861ac21fab0284f07096b0e399110215090
Author: Build Pelican (action) <[email protected]>
AuthorDate: Fri Aug 7 19:52:12 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 ca91107..a666f7e 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
@@ -156,9 +156,7 @@ whole subtree back to Spark. In 1.0 both support levels
route through the dispat
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>
-collations, <code>sort_array</code> under strict floating-point mode,
<code>multiply_dt_interval</code>, and interval dispatch
-for nested values and native shuffle.</p>
+rather than falling back, and more string, array, and interval expressions
were opted in as well.</p>
<p>Third, the path is now visible. Comet's extended explain output reports
native versus codegen-dispatch
coverage for a plan, so you can see which path each expression actually took
rather than inferring it from
the absence of a fallback reason.</p>
diff --git a/blog/feeds/all-en.atom.xml b/blog/feeds/all-en.atom.xml
index 41f4989..522c75f 100644
--- a/blog/feeds/all-en.atom.xml
+++ b/blog/feeds/all-en.atom.xml
@@ -101,9 +101,7 @@ whole subtree back to Spark. In 1.0 both support levels
route through the dispat
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>
-collations, <code>sort_array</code> under strict floating-point
mode, <code>multiply_dt_interval</code>, and interval dispatch
-for nested values and native shuffle.</p>
+rather than falling back, and more string, array, and interval expressions
were opted in as well.</p>
<p>Third, the path is now visible. Comet's extended explain output
reports native versus codegen-dispatch
coverage for a plan, so you can see which path each expression actually took
rather than inferring it from
the absence of a fallback reason.</p>
diff --git a/blog/feeds/blog.atom.xml b/blog/feeds/blog.atom.xml
index a4a4835..bf8dffe 100644
--- a/blog/feeds/blog.atom.xml
+++ b/blog/feeds/blog.atom.xml
@@ -101,9 +101,7 @@ whole subtree back to Spark. In 1.0 both support levels
route through the dispat
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>
-collations, <code>sort_array</code> under strict floating-point
mode, <code>multiply_dt_interval</code>, and interval dispatch
-for nested values and native shuffle.</p>
+rather than falling back, and more string, array, and interval expressions
were opted in as well.</p>
<p>Third, the path is now visible. Comet's extended explain output
reports native versus codegen-dispatch
coverage for a plan, so you can see which path each expression actually took
rather than inferring it from
the absence of a fallback reason.</p>
diff --git a/blog/feeds/pmc.atom.xml b/blog/feeds/pmc.atom.xml
index 697e759..849e212 100644
--- a/blog/feeds/pmc.atom.xml
+++ b/blog/feeds/pmc.atom.xml
@@ -101,9 +101,7 @@ whole subtree back to Spark. In 1.0 both support levels
route through the dispat
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>
-collations, <code>sort_array</code> under strict floating-point
mode, <code>multiply_dt_interval</code>, and interval dispatch
-for nested values and native shuffle.</p>
+rather than falling back, and more string, array, and interval expressions
were opted in as well.</p>
<p>Third, the path is now visible. Comet's extended explain output
reports native versus codegen-dispatch
coverage for a plan, so you can see which path each expression actually took
rather than inferring it from
the absence of a fallback reason.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
