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 6376658 Commit build products
6376658 is described below
commit 6376658acd13c04601bb10503160cc59ee9831d8
Author: Build Pelican (action) <[email protected]>
AuthorDate: Fri Aug 7 19:57:53 2026 +0000
Commit build products
---
blog/2026/08/07/datafusion-comet-1.0.0/index.html | 3 +--
blog/feeds/all-en.atom.xml | 3 +--
blog/feeds/blog.atom.xml | 3 +--
blog/feeds/pmc.atom.xml | 3 +--
4 files changed, 4 insertions(+), 8 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 c1e7727..a909d02 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
@@ -192,8 +192,7 @@ so Parquet statistics pruning can engage; filter pushdown
configuration has been
passes a metadata size hint so a single read usually captures the footer; and
the native Parquet scan seeds
its reader options from the session config so Parquet settings you already set
take effect.</p>
<h3 id="iceberg-table-format-v3">Iceberg Table Format V3<a class="headerlink"
href="#iceberg-table-format-v3" title="Permanent link">¶</a></h3>
-<p>Comet now supports Iceberg 1.11 and Iceberg table format V3 (with native
table decryption for V3 tables and
-fallback to Spark for other V3 features). The native Iceberg scan supports the
<code>_pos</code>, <code>_spec</code>, <code>_file</code>, and
+<p>Comet now supports Iceberg 1.11 and its first Iceberg table format V3
feature: full table encryption. Other V3 features like deletion vectors and new
data types (<em>e.g.</em>, <code>VARIANT</code>) fall back gracefully. The
native Iceberg scan supports the <code>_pos</code>, <code>_spec</code>,
<code>_file</code>, and
<code>_partition</code> metadata columns, sizes delete files correctly to
avoid dropped deletes, disambiguates scans that
share a <code>metadata_location</code>, and dedupes residuals and delete files
in the native scan serde. A prior case
where Iceberg native scan exchange reuse with different pushed filters could
produce wrong results is also
diff --git a/blog/feeds/all-en.atom.xml b/blog/feeds/all-en.atom.xml
index b984754..0a7a7dc 100644
--- a/blog/feeds/all-en.atom.xml
+++ b/blog/feeds/all-en.atom.xml
@@ -137,8 +137,7 @@ so Parquet statistics pruning can engage; filter pushdown
configuration has been
passes a metadata size hint so a single read usually captures the footer; and
the native Parquet scan seeds
its reader options from the session config so Parquet settings you already set
take effect.</p>
<h3 id="iceberg-table-format-v3">Iceberg Table Format V3<a
class="headerlink" href="#iceberg-table-format-v3" title="Permanent
link">¶</a></h3>
-<p>Comet now supports Iceberg 1.11 and Iceberg table format V3 (with
native table decryption for V3 tables and
-fallback to Spark for other V3 features). The native Iceberg scan supports the
<code>_pos</code>, <code>_spec</code>,
<code>_file</code>, and
+<p>Comet now supports Iceberg 1.11 and its first Iceberg table format V3
feature: full table encryption. Other V3 features like deletion vectors and new
data types (<em>e.g.</em>, <code>VARIANT</code>) fall
back gracefully. The native Iceberg scan supports the
<code>_pos</code>, <code>_spec</code>,
<code>_file</code>, and
<code>_partition</code> metadata columns, sizes delete files
correctly to avoid dropped deletes, disambiguates scans that
share a <code>metadata_location</code>, and dedupes residuals and
delete files in the native scan serde. A prior case
where Iceberg native scan exchange reuse with different pushed filters could
produce wrong results is also
diff --git a/blog/feeds/blog.atom.xml b/blog/feeds/blog.atom.xml
index a28f6fa..87629b6 100644
--- a/blog/feeds/blog.atom.xml
+++ b/blog/feeds/blog.atom.xml
@@ -137,8 +137,7 @@ so Parquet statistics pruning can engage; filter pushdown
configuration has been
passes a metadata size hint so a single read usually captures the footer; and
the native Parquet scan seeds
its reader options from the session config so Parquet settings you already set
take effect.</p>
<h3 id="iceberg-table-format-v3">Iceberg Table Format V3<a
class="headerlink" href="#iceberg-table-format-v3" title="Permanent
link">¶</a></h3>
-<p>Comet now supports Iceberg 1.11 and Iceberg table format V3 (with
native table decryption for V3 tables and
-fallback to Spark for other V3 features). The native Iceberg scan supports the
<code>_pos</code>, <code>_spec</code>,
<code>_file</code>, and
+<p>Comet now supports Iceberg 1.11 and its first Iceberg table format V3
feature: full table encryption. Other V3 features like deletion vectors and new
data types (<em>e.g.</em>, <code>VARIANT</code>) fall
back gracefully. The native Iceberg scan supports the
<code>_pos</code>, <code>_spec</code>,
<code>_file</code>, and
<code>_partition</code> metadata columns, sizes delete files
correctly to avoid dropped deletes, disambiguates scans that
share a <code>metadata_location</code>, and dedupes residuals and
delete files in the native scan serde. A prior case
where Iceberg native scan exchange reuse with different pushed filters could
produce wrong results is also
diff --git a/blog/feeds/pmc.atom.xml b/blog/feeds/pmc.atom.xml
index 19a8e2b..8509a6b 100644
--- a/blog/feeds/pmc.atom.xml
+++ b/blog/feeds/pmc.atom.xml
@@ -137,8 +137,7 @@ so Parquet statistics pruning can engage; filter pushdown
configuration has been
passes a metadata size hint so a single read usually captures the footer; and
the native Parquet scan seeds
its reader options from the session config so Parquet settings you already set
take effect.</p>
<h3 id="iceberg-table-format-v3">Iceberg Table Format V3<a
class="headerlink" href="#iceberg-table-format-v3" title="Permanent
link">¶</a></h3>
-<p>Comet now supports Iceberg 1.11 and Iceberg table format V3 (with
native table decryption for V3 tables and
-fallback to Spark for other V3 features). The native Iceberg scan supports the
<code>_pos</code>, <code>_spec</code>,
<code>_file</code>, and
+<p>Comet now supports Iceberg 1.11 and its first Iceberg table format V3
feature: full table encryption. Other V3 features like deletion vectors and new
data types (<em>e.g.</em>, <code>VARIANT</code>) fall
back gracefully. The native Iceberg scan supports the
<code>_pos</code>, <code>_spec</code>,
<code>_file</code>, and
<code>_partition</code> metadata columns, sizes delete files
correctly to avoid dropped deletes, disambiguates scans that
share a <code>metadata_location</code>, and dedupes residuals and
delete files in the native scan serde. A prior case
where Iceberg native scan exchange reuse with different pushed filters could
produce wrong results is also
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
