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 b810d31 Commit build products
b810d31 is described below
commit b810d31e24225630ab351793ed71b223fb216d96
Author: Build Pelican (action) <[email protected]>
AuthorDate: Tue Aug 4 17:25:26 2026 +0000
Commit build products
---
blog/2026/08/07/datafusion-comet-1.0.0/index.html | 11 ++++++-----
blog/feeds/all-en.atom.xml | 11 ++++++-----
blog/feeds/blog.atom.xml | 11 ++++++-----
blog/feeds/pmc.atom.xml | 11 ++++++-----
4 files changed, 24 insertions(+), 20 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 2030729..a995c1b 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,11 +153,12 @@ boundary, so this shrinks per-query overhead across the
board. Plan-data injecti
operator kind and no longer rebuilds operators it does not touch. Comet also
makes far fewer timer calls in
the native execution loop.</p>
<h2 id="correctness">Correctness<a class="headerlink" href="#correctness"
title="Permanent link">¶</a></h2>
-<p>A 1.0 release is only as good as its results. This release fixes roughly 30
divergences from Spark, spanning
-casts, ANSI error semantics, wrong-result bugs, string and encoding handling,
collations, and error
-reporting. Most were found by running extensive AI-assisted audit sweeps of
the code base, comparing Comet's
-expression implementations with all supported versions of Spark. See the <a
href="https://github.com/apache/datafusion-comet/blob/main/docs/source/changelog/1.0.0.md";>change
log</a> for the full list; two
-representative fixes give a sense of the shape of the work:</p>
+<p>Correctness fixes have been a regular part of every Comet release, but for
1.0 we made an extra push to
+clear out the bulk of the known issues before drawing a line under the stable
release. This release fixes
+roughly 30 divergences from Spark, spanning casts, ANSI error semantics,
wrong-result bugs, string and
+encoding handling, collations, and error reporting. Most were found by running
extensive AI-assisted audit
+sweeps of the code base, comparing Comet's expression implementations with all
supported versions of Spark.
+See the <a
href="https://github.com/apache/datafusion-comet/blob/main/docs/source/changelog/1.0.0.md";>change
log</a> for the full list; two representative fixes give a sense of the shape
of the work:</p>
<ul>
<li><strong>Whitespace trimming in string-to-numeric casts.</strong> Casts to
<code>boolean</code>, integral types, <code>float</code>/<code>double</code>,
and <code>decimal</code> now use Spark's exact trim rules. Comet's kernels
had used four different trim sets, three of
diff --git a/blog/feeds/all-en.atom.xml b/blog/feeds/all-en.atom.xml
index fdde10b..6575186 100644
--- a/blog/feeds/all-en.atom.xml
+++ b/blog/feeds/all-en.atom.xml
@@ -101,11 +101,12 @@ boundary, so this shrinks per-query overhead across the
board. Plan-data injecti
operator kind and no longer rebuilds operators it does not touch. Comet also
makes far fewer timer calls in
the native execution loop.</p>
<h2 id="correctness">Correctness<a class="headerlink"
href="#correctness" title="Permanent link">¶</a></h2>
-<p>A 1.0 release is only as good as its results. This release fixes
roughly 30 divergences from Spark, spanning
-casts, ANSI error semantics, wrong-result bugs, string and encoding handling,
collations, and error
-reporting. Most were found by running extensive AI-assisted audit sweeps of
the code base, comparing Comet's
-expression implementations with all supported versions of Spark. See the <a
href="https://github.com/apache/datafusion-comet/blob/main/docs/source/changelog/1.0.0.md">change
log</a> for the full list; two
-representative fixes give a sense of the shape of the work:</p>
+<p>Correctness fixes have been a regular part of every Comet release,
but for 1.0 we made an extra push to
+clear out the bulk of the known issues before drawing a line under the stable
release. This release fixes
+roughly 30 divergences from Spark, spanning casts, ANSI error semantics,
wrong-result bugs, string and
+encoding handling, collations, and error reporting. Most were found by running
extensive AI-assisted audit
+sweeps of the code base, comparing Comet's expression implementations with all
supported versions of Spark.
+See the <a
href="https://github.com/apache/datafusion-comet/blob/main/docs/source/changelog/1.0.0.md">change
log</a> for the full list; two representative fixes give a sense of the
shape of the work:</p>
<ul>
<li><strong>Whitespace trimming in string-to-numeric
casts.</strong> Casts to <code>boolean</code>, integral
types, <code>float</code>/<code>double</code>,
and <code>decimal</code> now use Spark's exact trim rules.
Comet's kernels had used four different trim sets, three of
diff --git a/blog/feeds/blog.atom.xml b/blog/feeds/blog.atom.xml
index c8d7c18..6981629 100644
--- a/blog/feeds/blog.atom.xml
+++ b/blog/feeds/blog.atom.xml
@@ -101,11 +101,12 @@ boundary, so this shrinks per-query overhead across the
board. Plan-data injecti
operator kind and no longer rebuilds operators it does not touch. Comet also
makes far fewer timer calls in
the native execution loop.</p>
<h2 id="correctness">Correctness<a class="headerlink"
href="#correctness" title="Permanent link">¶</a></h2>
-<p>A 1.0 release is only as good as its results. This release fixes
roughly 30 divergences from Spark, spanning
-casts, ANSI error semantics, wrong-result bugs, string and encoding handling,
collations, and error
-reporting. Most were found by running extensive AI-assisted audit sweeps of
the code base, comparing Comet's
-expression implementations with all supported versions of Spark. See the <a
href="https://github.com/apache/datafusion-comet/blob/main/docs/source/changelog/1.0.0.md">change
log</a> for the full list; two
-representative fixes give a sense of the shape of the work:</p>
+<p>Correctness fixes have been a regular part of every Comet release,
but for 1.0 we made an extra push to
+clear out the bulk of the known issues before drawing a line under the stable
release. This release fixes
+roughly 30 divergences from Spark, spanning casts, ANSI error semantics,
wrong-result bugs, string and
+encoding handling, collations, and error reporting. Most were found by running
extensive AI-assisted audit
+sweeps of the code base, comparing Comet's expression implementations with all
supported versions of Spark.
+See the <a
href="https://github.com/apache/datafusion-comet/blob/main/docs/source/changelog/1.0.0.md">change
log</a> for the full list; two representative fixes give a sense of the
shape of the work:</p>
<ul>
<li><strong>Whitespace trimming in string-to-numeric
casts.</strong> Casts to <code>boolean</code>, integral
types, <code>float</code>/<code>double</code>,
and <code>decimal</code> now use Spark's exact trim rules.
Comet's kernels had used four different trim sets, three of
diff --git a/blog/feeds/pmc.atom.xml b/blog/feeds/pmc.atom.xml
index 9441b15..2a24dc0 100644
--- a/blog/feeds/pmc.atom.xml
+++ b/blog/feeds/pmc.atom.xml
@@ -101,11 +101,12 @@ boundary, so this shrinks per-query overhead across the
board. Plan-data injecti
operator kind and no longer rebuilds operators it does not touch. Comet also
makes far fewer timer calls in
the native execution loop.</p>
<h2 id="correctness">Correctness<a class="headerlink"
href="#correctness" title="Permanent link">¶</a></h2>
-<p>A 1.0 release is only as good as its results. This release fixes
roughly 30 divergences from Spark, spanning
-casts, ANSI error semantics, wrong-result bugs, string and encoding handling,
collations, and error
-reporting. Most were found by running extensive AI-assisted audit sweeps of
the code base, comparing Comet's
-expression implementations with all supported versions of Spark. See the <a
href="https://github.com/apache/datafusion-comet/blob/main/docs/source/changelog/1.0.0.md">change
log</a> for the full list; two
-representative fixes give a sense of the shape of the work:</p>
+<p>Correctness fixes have been a regular part of every Comet release,
but for 1.0 we made an extra push to
+clear out the bulk of the known issues before drawing a line under the stable
release. This release fixes
+roughly 30 divergences from Spark, spanning casts, ANSI error semantics,
wrong-result bugs, string and
+encoding handling, collations, and error reporting. Most were found by running
extensive AI-assisted audit
+sweeps of the code base, comparing Comet's expression implementations with all
supported versions of Spark.
+See the <a
href="https://github.com/apache/datafusion-comet/blob/main/docs/source/changelog/1.0.0.md">change
log</a> for the full list; two representative fixes give a sense of the
shape of the work:</p>
<ul>
<li><strong>Whitespace trimming in string-to-numeric
casts.</strong> Casts to <code>boolean</code>, integral
types, <code>float</code>/<code>double</code>,
and <code>decimal</code> now use Spark's exact trim rules.
Comet's kernels had used four different trim sets, three of
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
