This is an automated email from the ASF dual-hosted git repository.
github-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 2f8397f Commit build products
2f8397f is described below
commit 2f8397ff0cb2e94d8bdf49ae70aec319357b9e08
Author: Build Pelican (action) <[email protected]>
AuthorDate: Sat Jan 10 19:56:12 2026 +0000
Commit build products
---
blog/2026/01/08/datafusion-52.0.0/index.html | 15 +++++++++++----
blog/feeds/all-en.atom.xml | 15 +++++++++++----
blog/feeds/blog.atom.xml | 15 +++++++++++----
blog/feeds/pmc.atom.xml | 15 +++++++++++----
4 files changed, 44 insertions(+), 16 deletions(-)
diff --git a/blog/2026/01/08/datafusion-52.0.0/index.html
b/blog/2026/01/08/datafusion-52.0.0/index.html
index f13b172..b1a4498 100644
--- a/blog/2026/01/08/datafusion-52.0.0/index.html
+++ b/blog/2026/01/08/datafusion-52.0.0/index.html
@@ -225,9 +225,14 @@ own mutation logic.</p>
</code></pre>
<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/19142";>#19142</a></p>
<h3
id="coalescebatchesexec-removal-and-integrated-batch-coalescing">CoalesceBatchesExec
removal and integrated batch coalescing<a class="headerlink"
href="#coalescebatchesexec-removal-and-integrated-batch-coalescing"
title="Permanent link">¶</a></h3>
-<p>DataFusion continues the work to remove the standalone CoalesceBatchesExec
-operator (<a
href="https://github.com/apache/datafusion/issues/18779";>#18779</a>). Batch
coalescing is now integrated into multiple operators,
-reducing plan complexity and avoiding unnecessary batch materialization.</p>
+<p>DataFusion continues the work from the CoalesceBatchesExec epic (<a
href="https://github.com/apache/datafusion/issues/18779";>#18779</a>). The
+standalone <code>CoalesceBatchesExec</code> operator existed to ensure batches
were large
+enough for vectorized execution, and it was inserted after filter-like
+operators such as <code>FilterExec</code>, <code>HashJoinExec</code>, and
<code>RepartitionExec</code>. However,
+it also blocked other optimizations (like pushing limits through joins) and
+made optimizer rules more complex. This release integrates coalescing into the
+operators themselves and relies on Arrow's coalesce kernels, reducing plan
+complexity while keeping batch sizes efficient.</p>
<p>Diagram:</p>
<pre><code>Before:
Scan -> CoalesceBatches -> Filter -> CoalesceBatches -> Join
@@ -235,7 +240,9 @@ reducing plan complexity and avoiding unnecessary batch
materialization.</p>
After:
Scan -> Filter (coalesce inline) -> Join (coalesce inline)
</code></pre>
-<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18540";>#18540</a>, <a
href="https://github.com/apache/datafusion/pull/18604";>#18604</a>, <a
href="https://github.com/apache/datafusion/pull/18630";>#18630</a>, <a
href="https://github.com/apache/datafusion/pull/18972";>#18972</a>, <a
href="https://github.com/apache/datafusion/pull/19002";>#19002</a>, <a
href="https://github.com/apache/datafusion/pull/19342";>#19342</a>, <a
href="https://github.com/apache/datafusion/pull/19239 [...]
+<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18540";>#18540</a>, <a
href="https://github.com/apache/datafusion/pull/18604";>#18604</a>, <a
href="https://github.com/apache/datafusion/pull/18630";>#18630</a>, <a
href="https://github.com/apache/datafusion/pull/18972";>#18972</a>, <a
href="https://github.com/apache/datafusion/pull/19002";>#19002</a>, <a
href="https://github.com/apache/datafusion/pull/19342";>#19342</a>, <a
href="https://github.com/apache/datafusion/pull/19239 [...]
+Thanks to <a href="https://github.com/Tim-53";>Tim-53</a>, <a
href="https://github.com/Dandandan";>Dandandan</a>, <a
href="https://github.com/jizezhang";>jizezhang</a>, and <a
href="https://github.com/feniljain";>feniljain</a> for implementing
+this feature.</p>
<h2 id="upgrade-guide-and-changelog">Upgrade Guide and Changelog<a
class="headerlink" href="#upgrade-guide-and-changelog" title="Permanent
link">¶</a></h2>
<p>Upgrading to 52.0.0 should be straightforward for most users. Please review
the
<a
href="https://datafusion.apache.org/library-user-guide/upgrading.html";>Upgrade
Guide</a>
diff --git a/blog/feeds/all-en.atom.xml b/blog/feeds/all-en.atom.xml
index 0e2ab80..335fd4f 100644
--- a/blog/feeds/all-en.atom.xml
+++ b/blog/feeds/all-en.atom.xml
@@ -177,9 +177,14 @@ own mutation logic.</p>
</code></pre>
<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/19142">#19142</a></p>
<h3
id="coalescebatchesexec-removal-and-integrated-batch-coalescing">CoalesceBatchesExec
removal and integrated batch coalescing<a class="headerlink"
href="#coalescebatchesexec-removal-and-integrated-batch-coalescing"
title="Permanent link">¶</a></h3>
-<p>DataFusion continues the work to remove the standalone
CoalesceBatchesExec
-operator (<a
href="https://github.com/apache/datafusion/issues/18779">#18779</a>).
Batch coalescing is now integrated into multiple operators,
-reducing plan complexity and avoiding unnecessary batch
materialization.</p>
+<p>DataFusion continues the work from the CoalesceBatchesExec epic
(<a
href="https://github.com/apache/datafusion/issues/18779">#18779</a>).
The
+standalone <code>CoalesceBatchesExec</code> operator existed to
ensure batches were large
+enough for vectorized execution, and it was inserted after filter-like
+operators such as <code>FilterExec</code>,
<code>HashJoinExec</code>, and
<code>RepartitionExec</code>. However,
+it also blocked other optimizations (like pushing limits through joins) and
+made optimizer rules more complex. This release integrates coalescing into the
+operators themselves and relies on Arrow's coalesce kernels, reducing plan
+complexity while keeping batch sizes efficient.</p>
<p>Diagram:</p>
<pre><code>Before:
Scan -&gt; CoalesceBatches -&gt; Filter -&gt; CoalesceBatches
-&gt; Join
@@ -187,7 +192,9 @@ reducing plan complexity and avoiding unnecessary batch
materialization.</p&g
After:
Scan -&gt; Filter (coalesce inline) -&gt; Join (coalesce inline)
</code></pre>
-<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18540">#18540</a>,
<a
href="https://github.com/apache/datafusion/pull/18604">#18604</a>,
<a
href="https://github.com/apache/datafusion/pull/18630">#18630</a>,
<a
href="https://github.com/apache/datafusion/pull/18972">#18972</a>,
<a
href="https://github.com/apache/datafusion/pull/19002">#19002</a>,
<a href="https://github.com/apache/datafusion/pull/19342"; [...]
+<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18540">#18540</a>,
<a
href="https://github.com/apache/datafusion/pull/18604">#18604</a>,
<a
href="https://github.com/apache/datafusion/pull/18630">#18630</a>,
<a
href="https://github.com/apache/datafusion/pull/18972">#18972</a>,
<a
href="https://github.com/apache/datafusion/pull/19002">#19002</a>,
<a href="https://github.com/apache/datafusion/pull/19342"; [...]
+Thanks to <a href="https://github.com/Tim-53">Tim-53</a>, <a
href="https://github.com/Dandandan">Dandandan</a>, <a
href="https://github.com/jizezhang">jizezhang</a>, and <a
href="https://github.com/feniljain">feniljain</a> for implementing
+this feature.</p>
<h2 id="upgrade-guide-and-changelog">Upgrade Guide and Changelog<a
class="headerlink" href="#upgrade-guide-and-changelog" title="Permanent
link">¶</a></h2>
<p>Upgrading to 52.0.0 should be straightforward for most users. Please
review the
<a
href="https://datafusion.apache.org/library-user-guide/upgrading.html">Upgrade
Guide</a>
diff --git a/blog/feeds/blog.atom.xml b/blog/feeds/blog.atom.xml
index ca53439..c53ad62 100644
--- a/blog/feeds/blog.atom.xml
+++ b/blog/feeds/blog.atom.xml
@@ -177,9 +177,14 @@ own mutation logic.</p>
</code></pre>
<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/19142">#19142</a></p>
<h3
id="coalescebatchesexec-removal-and-integrated-batch-coalescing">CoalesceBatchesExec
removal and integrated batch coalescing<a class="headerlink"
href="#coalescebatchesexec-removal-and-integrated-batch-coalescing"
title="Permanent link">¶</a></h3>
-<p>DataFusion continues the work to remove the standalone
CoalesceBatchesExec
-operator (<a
href="https://github.com/apache/datafusion/issues/18779">#18779</a>).
Batch coalescing is now integrated into multiple operators,
-reducing plan complexity and avoiding unnecessary batch
materialization.</p>
+<p>DataFusion continues the work from the CoalesceBatchesExec epic
(<a
href="https://github.com/apache/datafusion/issues/18779">#18779</a>).
The
+standalone <code>CoalesceBatchesExec</code> operator existed to
ensure batches were large
+enough for vectorized execution, and it was inserted after filter-like
+operators such as <code>FilterExec</code>,
<code>HashJoinExec</code>, and
<code>RepartitionExec</code>. However,
+it also blocked other optimizations (like pushing limits through joins) and
+made optimizer rules more complex. This release integrates coalescing into the
+operators themselves and relies on Arrow's coalesce kernels, reducing plan
+complexity while keeping batch sizes efficient.</p>
<p>Diagram:</p>
<pre><code>Before:
Scan -&gt; CoalesceBatches -&gt; Filter -&gt; CoalesceBatches
-&gt; Join
@@ -187,7 +192,9 @@ reducing plan complexity and avoiding unnecessary batch
materialization.</p&g
After:
Scan -&gt; Filter (coalesce inline) -&gt; Join (coalesce inline)
</code></pre>
-<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18540">#18540</a>,
<a
href="https://github.com/apache/datafusion/pull/18604">#18604</a>,
<a
href="https://github.com/apache/datafusion/pull/18630">#18630</a>,
<a
href="https://github.com/apache/datafusion/pull/18972">#18972</a>,
<a
href="https://github.com/apache/datafusion/pull/19002">#19002</a>,
<a href="https://github.com/apache/datafusion/pull/19342"; [...]
+<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18540">#18540</a>,
<a
href="https://github.com/apache/datafusion/pull/18604">#18604</a>,
<a
href="https://github.com/apache/datafusion/pull/18630">#18630</a>,
<a
href="https://github.com/apache/datafusion/pull/18972">#18972</a>,
<a
href="https://github.com/apache/datafusion/pull/19002">#19002</a>,
<a href="https://github.com/apache/datafusion/pull/19342"; [...]
+Thanks to <a href="https://github.com/Tim-53">Tim-53</a>, <a
href="https://github.com/Dandandan">Dandandan</a>, <a
href="https://github.com/jizezhang">jizezhang</a>, and <a
href="https://github.com/feniljain">feniljain</a> for implementing
+this feature.</p>
<h2 id="upgrade-guide-and-changelog">Upgrade Guide and Changelog<a
class="headerlink" href="#upgrade-guide-and-changelog" title="Permanent
link">¶</a></h2>
<p>Upgrading to 52.0.0 should be straightforward for most users. Please
review the
<a
href="https://datafusion.apache.org/library-user-guide/upgrading.html">Upgrade
Guide</a>
diff --git a/blog/feeds/pmc.atom.xml b/blog/feeds/pmc.atom.xml
index f0cf9b7..40c024b 100644
--- a/blog/feeds/pmc.atom.xml
+++ b/blog/feeds/pmc.atom.xml
@@ -177,9 +177,14 @@ own mutation logic.</p>
</code></pre>
<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/19142">#19142</a></p>
<h3
id="coalescebatchesexec-removal-and-integrated-batch-coalescing">CoalesceBatchesExec
removal and integrated batch coalescing<a class="headerlink"
href="#coalescebatchesexec-removal-and-integrated-batch-coalescing"
title="Permanent link">¶</a></h3>
-<p>DataFusion continues the work to remove the standalone
CoalesceBatchesExec
-operator (<a
href="https://github.com/apache/datafusion/issues/18779">#18779</a>).
Batch coalescing is now integrated into multiple operators,
-reducing plan complexity and avoiding unnecessary batch
materialization.</p>
+<p>DataFusion continues the work from the CoalesceBatchesExec epic
(<a
href="https://github.com/apache/datafusion/issues/18779">#18779</a>).
The
+standalone <code>CoalesceBatchesExec</code> operator existed to
ensure batches were large
+enough for vectorized execution, and it was inserted after filter-like
+operators such as <code>FilterExec</code>,
<code>HashJoinExec</code>, and
<code>RepartitionExec</code>. However,
+it also blocked other optimizations (like pushing limits through joins) and
+made optimizer rules more complex. This release integrates coalescing into the
+operators themselves and relies on Arrow's coalesce kernels, reducing plan
+complexity while keeping batch sizes efficient.</p>
<p>Diagram:</p>
<pre><code>Before:
Scan -&gt; CoalesceBatches -&gt; Filter -&gt; CoalesceBatches
-&gt; Join
@@ -187,7 +192,9 @@ reducing plan complexity and avoiding unnecessary batch
materialization.</p&g
After:
Scan -&gt; Filter (coalesce inline) -&gt; Join (coalesce inline)
</code></pre>
-<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18540">#18540</a>,
<a
href="https://github.com/apache/datafusion/pull/18604">#18604</a>,
<a
href="https://github.com/apache/datafusion/pull/18630">#18630</a>,
<a
href="https://github.com/apache/datafusion/pull/18972">#18972</a>,
<a
href="https://github.com/apache/datafusion/pull/19002">#19002</a>,
<a href="https://github.com/apache/datafusion/pull/19342"; [...]
+<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18540">#18540</a>,
<a
href="https://github.com/apache/datafusion/pull/18604">#18604</a>,
<a
href="https://github.com/apache/datafusion/pull/18630">#18630</a>,
<a
href="https://github.com/apache/datafusion/pull/18972">#18972</a>,
<a
href="https://github.com/apache/datafusion/pull/19002">#19002</a>,
<a href="https://github.com/apache/datafusion/pull/19342"; [...]
+Thanks to <a href="https://github.com/Tim-53">Tim-53</a>, <a
href="https://github.com/Dandandan">Dandandan</a>, <a
href="https://github.com/jizezhang">jizezhang</a>, and <a
href="https://github.com/feniljain">feniljain</a> for implementing
+this feature.</p>
<h2 id="upgrade-guide-and-changelog">Upgrade Guide and Changelog<a
class="headerlink" href="#upgrade-guide-and-changelog" title="Permanent
link">¶</a></h2>
<p>Upgrading to 52.0.0 should be straightforward for most users. Please
review the
<a
href="https://datafusion.apache.org/library-user-guide/upgrading.html">Upgrade
Guide</a>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
