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 6c17a68 Commit build products
6c17a68 is described below
commit 6c17a68e372a26798931e4081bdae3073937902d
Author: Build Pelican (action) <[email protected]>
AuthorDate: Sat Jan 24 12:03:26 2026 +0000
Commit build products
---
blog/2026/01/08/datafusion-52.0.0/index.html | 7 ++++---
blog/feeds/all-en.atom.xml | 7 ++++---
blog/feeds/blog.atom.xml | 7 ++++---
blog/feeds/pmc.atom.xml | 7 ++++---
4 files changed, 16 insertions(+), 12 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 9d9ab8a..cf9383e 100644
--- a/blog/2026/01/08/datafusion-52.0.0/index.html
+++ b/blog/2026/01/08/datafusion-52.0.0/index.html
@@ -193,9 +193,10 @@ LOCATION 's3://bucket/events.arrow';
<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18457";>#18457</a></p>
<h3 id="more-extensible-sql-planning-with-relationplanner">More Extensible SQL
Planning with <code>RelationPlanner</code><a class="headerlink"
href="#more-extensible-sql-planning-with-relationplanner" title="Permanent
link">¶</a></h3>
<p>DataFusion now has an API for extending the SQL planner for relations, as
-explained in the <a
href="https://datafusion.apache.org/blog/2026/01/12/extending-sql/";>Extending
SQL in DataFusion Blog</a>. With this new API, you can
-customize DataFusion to support almost any SQL syntax, such as the following
-(which are not supported by default):</p>
+explained in the <a
href="https://datafusion.apache.org/blog/2026/01/12/extending-sql/";>Extending
SQL in DataFusion Blog</a>. In addition to the existing
+expression and types extension points, this new API now allows extending
<code>FROM</code>
+clauses. Using these APIs it is straightforward to provide SQL support for
+almost any dialect, including vendor-specific syntax. Example use cases
include:</p>
<pre><code class="language-sql">-- Postgres-style JSON operators
SELECT payload->'user'->>'id' FROM logs;
-- MySQL-specific types
diff --git a/blog/feeds/all-en.atom.xml b/blog/feeds/all-en.atom.xml
index e207d9c..0780248 100644
--- a/blog/feeds/all-en.atom.xml
+++ b/blog/feeds/all-en.atom.xml
@@ -430,9 +430,10 @@ LOCATION 's3://bucket/events.arrow';
<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18457">#18457</a></p>
<h3 id="more-extensible-sql-planning-with-relationplanner">More
Extensible SQL Planning with <code>RelationPlanner</code><a
class="headerlink" href="#more-extensible-sql-planning-with-relationplanner"
title="Permanent link">¶</a></h3>
<p>DataFusion now has an API for extending the SQL planner for
relations, as
-explained in the <a
href="https://datafusion.apache.org/blog/2026/01/12/extending-sql/">Extending
SQL in DataFusion Blog</a>. With this new API, you can
-customize DataFusion to support almost any SQL syntax, such as the following
-(which are not supported by default):</p>
+explained in the <a
href="https://datafusion.apache.org/blog/2026/01/12/extending-sql/">Extending
SQL in DataFusion Blog</a>. In addition to the existing
+expression and types extension points, this new API now allows extending
<code>FROM</code>
+clauses. Using these APIs it is straightforward to provide SQL support for
+almost any dialect, including vendor-specific syntax. Example use cases
include:</p>
<pre><code class="language-sql">-- Postgres-style JSON operators
SELECT payload-&gt;'user'-&gt;&gt;'id' FROM logs;
-- MySQL-specific types
diff --git a/blog/feeds/blog.atom.xml b/blog/feeds/blog.atom.xml
index 0edf0ba..78d6f6c 100644
--- a/blog/feeds/blog.atom.xml
+++ b/blog/feeds/blog.atom.xml
@@ -430,9 +430,10 @@ LOCATION 's3://bucket/events.arrow';
<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18457">#18457</a></p>
<h3 id="more-extensible-sql-planning-with-relationplanner">More
Extensible SQL Planning with <code>RelationPlanner</code><a
class="headerlink" href="#more-extensible-sql-planning-with-relationplanner"
title="Permanent link">¶</a></h3>
<p>DataFusion now has an API for extending the SQL planner for
relations, as
-explained in the <a
href="https://datafusion.apache.org/blog/2026/01/12/extending-sql/">Extending
SQL in DataFusion Blog</a>. With this new API, you can
-customize DataFusion to support almost any SQL syntax, such as the following
-(which are not supported by default):</p>
+explained in the <a
href="https://datafusion.apache.org/blog/2026/01/12/extending-sql/">Extending
SQL in DataFusion Blog</a>. In addition to the existing
+expression and types extension points, this new API now allows extending
<code>FROM</code>
+clauses. Using these APIs it is straightforward to provide SQL support for
+almost any dialect, including vendor-specific syntax. Example use cases
include:</p>
<pre><code class="language-sql">-- Postgres-style JSON operators
SELECT payload-&gt;'user'-&gt;&gt;'id' FROM logs;
-- MySQL-specific types
diff --git a/blog/feeds/pmc.atom.xml b/blog/feeds/pmc.atom.xml
index 63cd4f3..7091d9f 100644
--- a/blog/feeds/pmc.atom.xml
+++ b/blog/feeds/pmc.atom.xml
@@ -146,9 +146,10 @@ LOCATION 's3://bucket/events.arrow';
<p>Related PRs: <a
href="https://github.com/apache/datafusion/pull/18457">#18457</a></p>
<h3 id="more-extensible-sql-planning-with-relationplanner">More
Extensible SQL Planning with <code>RelationPlanner</code><a
class="headerlink" href="#more-extensible-sql-planning-with-relationplanner"
title="Permanent link">¶</a></h3>
<p>DataFusion now has an API for extending the SQL planner for
relations, as
-explained in the <a
href="https://datafusion.apache.org/blog/2026/01/12/extending-sql/">Extending
SQL in DataFusion Blog</a>. With this new API, you can
-customize DataFusion to support almost any SQL syntax, such as the following
-(which are not supported by default):</p>
+explained in the <a
href="https://datafusion.apache.org/blog/2026/01/12/extending-sql/">Extending
SQL in DataFusion Blog</a>. In addition to the existing
+expression and types extension points, this new API now allows extending
<code>FROM</code>
+clauses. Using these APIs it is straightforward to provide SQL support for
+almost any dialect, including vendor-specific syntax. Example use cases
include:</p>
<pre><code class="language-sql">-- Postgres-style JSON operators
SELECT payload-&gt;'user'-&gt;&gt;'id' FROM logs;
-- MySQL-specific types
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
