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 8cdefaf  Commit build products
8cdefaf is described below

commit 8cdefafce468b856aa7a956d5c4fa20678cf06b2
Author: Build Pelican (action) <priv...@infra.apache.org>
AuthorDate: Thu Mar 20 20:53:37 2025 +0000

    Commit build products
---
 blog/2025/03/20/datafusion-comet-0.7.0/index.html | 2 +-
 blog/feeds/all-en.atom.xml                        | 2 +-
 blog/feeds/blog.atom.xml                          | 2 +-
 blog/feeds/pmc.atom.xml                           | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/blog/2025/03/20/datafusion-comet-0.7.0/index.html 
b/blog/2025/03/20/datafusion-comet-0.7.0/index.html
index 7b80fc5..763cd9e 100644
--- a/blog/2025/03/20/datafusion-comet-0.7.0/index.html
+++ b/blog/2025/03/20/datafusion-comet-0.7.0/index.html
@@ -98,7 +98,7 @@ will now do a better job of picking the optimal build side. 
Thanks to <a href="h
 <h2>Experimental Support for DataFusion&rsquo;s DataSourceExec</h2>
 <p>It is now possible to configure Comet to use DataFusion&rsquo;s 
<code>DataSourceExec</code> instead of Comet&rsquo;s current Parquet reader. 
 Support should still be considered experimental, but most of Comet&rsquo;s 
unit tests are now passing with the new reader. 
-Known issues include handling of <code>INT96</code> timestamps and negative 
bytes and shorts.</p>
+Known issues include handling of <code>INT96</code> timestamps and unsigned 
bytes and shorts.</p>
 <p>To enable DataFusion&rsquo;s <code>DataSourceExec</code>, either set 
<code>spark.comet.scan.impl=native_datafusion</code> or set the environment 
 variable <code>COMET_PARQUET_SCAN_IMPL=native_datafusion</code>.</p>
 <h2>Complex Type Support</h2>
diff --git a/blog/feeds/all-en.atom.xml b/blog/feeds/all-en.atom.xml
index 5d03759..037f4fa 100644
--- a/blog/feeds/all-en.atom.xml
+++ b/blog/feeds/all-en.atom.xml
@@ -75,7 +75,7 @@ will now do a better job of picking the optimal build side. 
Thanks to &lt;a href
 &lt;h2&gt;Experimental Support for DataFusion&amp;rsquo;s 
DataSourceExec&lt;/h2&gt;
 &lt;p&gt;It is now possible to configure Comet to use DataFusion&amp;rsquo;s 
&lt;code&gt;DataSourceExec&lt;/code&gt; instead of Comet&amp;rsquo;s current 
Parquet reader. 
 Support should still be considered experimental, but most of Comet&amp;rsquo;s 
unit tests are now passing with the new reader. 
-Known issues include handling of &lt;code&gt;INT96&lt;/code&gt; timestamps and 
negative bytes and shorts.&lt;/p&gt;
+Known issues include handling of &lt;code&gt;INT96&lt;/code&gt; timestamps and 
unsigned bytes and shorts.&lt;/p&gt;
 &lt;p&gt;To enable DataFusion&amp;rsquo;s 
&lt;code&gt;DataSourceExec&lt;/code&gt;, either set 
&lt;code&gt;spark.comet.scan.impl=native_datafusion&lt;/code&gt; or set the 
environment 
 variable 
&lt;code&gt;COMET_PARQUET_SCAN_IMPL=native_datafusion&lt;/code&gt;.&lt;/p&gt;
 &lt;h2&gt;Complex Type Support&lt;/h2&gt;
diff --git a/blog/feeds/blog.atom.xml b/blog/feeds/blog.atom.xml
index 6984145..c9d12e0 100644
--- a/blog/feeds/blog.atom.xml
+++ b/blog/feeds/blog.atom.xml
@@ -75,7 +75,7 @@ will now do a better job of picking the optimal build side. 
Thanks to &lt;a href
 &lt;h2&gt;Experimental Support for DataFusion&amp;rsquo;s 
DataSourceExec&lt;/h2&gt;
 &lt;p&gt;It is now possible to configure Comet to use DataFusion&amp;rsquo;s 
&lt;code&gt;DataSourceExec&lt;/code&gt; instead of Comet&amp;rsquo;s current 
Parquet reader. 
 Support should still be considered experimental, but most of Comet&amp;rsquo;s 
unit tests are now passing with the new reader. 
-Known issues include handling of &lt;code&gt;INT96&lt;/code&gt; timestamps and 
negative bytes and shorts.&lt;/p&gt;
+Known issues include handling of &lt;code&gt;INT96&lt;/code&gt; timestamps and 
unsigned bytes and shorts.&lt;/p&gt;
 &lt;p&gt;To enable DataFusion&amp;rsquo;s 
&lt;code&gt;DataSourceExec&lt;/code&gt;, either set 
&lt;code&gt;spark.comet.scan.impl=native_datafusion&lt;/code&gt; or set the 
environment 
 variable 
&lt;code&gt;COMET_PARQUET_SCAN_IMPL=native_datafusion&lt;/code&gt;.&lt;/p&gt;
 &lt;h2&gt;Complex Type Support&lt;/h2&gt;
diff --git a/blog/feeds/pmc.atom.xml b/blog/feeds/pmc.atom.xml
index 372146c..60b6dbe 100644
--- a/blog/feeds/pmc.atom.xml
+++ b/blog/feeds/pmc.atom.xml
@@ -75,7 +75,7 @@ will now do a better job of picking the optimal build side. 
Thanks to &lt;a href
 &lt;h2&gt;Experimental Support for DataFusion&amp;rsquo;s 
DataSourceExec&lt;/h2&gt;
 &lt;p&gt;It is now possible to configure Comet to use DataFusion&amp;rsquo;s 
&lt;code&gt;DataSourceExec&lt;/code&gt; instead of Comet&amp;rsquo;s current 
Parquet reader. 
 Support should still be considered experimental, but most of Comet&amp;rsquo;s 
unit tests are now passing with the new reader. 
-Known issues include handling of &lt;code&gt;INT96&lt;/code&gt; timestamps and 
negative bytes and shorts.&lt;/p&gt;
+Known issues include handling of &lt;code&gt;INT96&lt;/code&gt; timestamps and 
unsigned bytes and shorts.&lt;/p&gt;
 &lt;p&gt;To enable DataFusion&amp;rsquo;s 
&lt;code&gt;DataSourceExec&lt;/code&gt;, either set 
&lt;code&gt;spark.comet.scan.impl=native_datafusion&lt;/code&gt; or set the 
environment 
 variable 
&lt;code&gt;COMET_PARQUET_SCAN_IMPL=native_datafusion&lt;/code&gt;.&lt;/p&gt;
 &lt;h2&gt;Complex Type Support&lt;/h2&gt;


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@datafusion.apache.org
For additional commands, e-mail: commits-h...@datafusion.apache.org

Reply via email to