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 a3b8c23 Commit build products
a3b8c23 is described below
commit a3b8c2302b2d74884d31a90b4f862864bd29f561
Author: Build Pelican (action) <priv...@infra.apache.org>
AuthorDate: Wed Jul 30 11:37:06 2025 +0000
Commit build products
---
blog/2025/07/29/metadata-handling/index.html | 2 +-
blog/feeds/all-en.atom.xml | 2 +-
blog/feeds/blog.atom.xml | 2 +-
blog/feeds/tim-saucer-dewey-dunnington-andrew-lamb.atom.xml | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/blog/2025/07/29/metadata-handling/index.html
b/blog/2025/07/29/metadata-handling/index.html
index fd4a0a7..e91d23c 100644
--- a/blog/2025/07/29/metadata-handling/index.html
+++ b/blog/2025/07/29/metadata-handling/index.html
@@ -63,7 +63,7 @@ limitations under the License.
which enables a variety of interesting improvements. Now users can access
metadata on
the input columns to functions and produce metadata in the output.</p>
<p>Metadata is specified as a map of key-value pairs of strings. This extra
metadata is used
-by Arrow implementations implement <a
href="https://arrow.apache.org/docs/format/Columnar.html#format-metadata-extension-types";>extension
types</a> and can also be used to add
+by Arrow implementations to support <a
href="https://arrow.apache.org/docs/format/Columnar.html#format-metadata-extension-types";>extension
types</a> and can also be used to add
use case-specific context to a column of values where the formality of an
extension type
is not required. In previous versions of DataFusion field metadata was
propagated through
certain operations (e.g., renaming or selecting a column) but was not
accessible to others
diff --git a/blog/feeds/all-en.atom.xml b/blog/feeds/all-en.atom.xml
index d69e41f..d36a13b 100644
--- a/blog/feeds/all-en.atom.xml
+++ b/blog/feeds/all-en.atom.xml
@@ -38,7 +38,7 @@ limitations under the License.
which enables a variety of interesting improvements. Now users can access
metadata on
the input columns to functions and produce metadata in the output.</p>
<p>Metadata is specified as a map of key-value pairs of strings. This
extra metadata is used
-by Arrow implementations implement <a
href="https://arrow.apache.org/docs/format/Columnar.html#format-metadata-extension-types">extension
types</a> and can also be used to add
+by Arrow implementations to support <a
href="https://arrow.apache.org/docs/format/Columnar.html#format-metadata-extension-types">extension
types</a> and can also be used to add
use case-specific context to a column of values where the formality of an
extension type
is not required. In previous versions of DataFusion field metadata was
propagated through
certain operations (e.g., renaming or selecting a column) but was not
accessible to others
diff --git a/blog/feeds/blog.atom.xml b/blog/feeds/blog.atom.xml
index f88ed7a..9407936 100644
--- a/blog/feeds/blog.atom.xml
+++ b/blog/feeds/blog.atom.xml
@@ -38,7 +38,7 @@ limitations under the License.
which enables a variety of interesting improvements. Now users can access
metadata on
the input columns to functions and produce metadata in the output.</p>
<p>Metadata is specified as a map of key-value pairs of strings. This
extra metadata is used
-by Arrow implementations implement <a
href="https://arrow.apache.org/docs/format/Columnar.html#format-metadata-extension-types">extension
types</a> and can also be used to add
+by Arrow implementations to support <a
href="https://arrow.apache.org/docs/format/Columnar.html#format-metadata-extension-types">extension
types</a> and can also be used to add
use case-specific context to a column of values where the formality of an
extension type
is not required. In previous versions of DataFusion field metadata was
propagated through
certain operations (e.g., renaming or selecting a column) but was not
accessible to others
diff --git a/blog/feeds/tim-saucer-dewey-dunnington-andrew-lamb.atom.xml
b/blog/feeds/tim-saucer-dewey-dunnington-andrew-lamb.atom.xml
index 3ebd092..dbb2846 100644
--- a/blog/feeds/tim-saucer-dewey-dunnington-andrew-lamb.atom.xml
+++ b/blog/feeds/tim-saucer-dewey-dunnington-andrew-lamb.atom.xml
@@ -38,7 +38,7 @@ limitations under the License.
which enables a variety of interesting improvements. Now users can access
metadata on
the input columns to functions and produce metadata in the output.</p>
<p>Metadata is specified as a map of key-value pairs of strings. This
extra metadata is used
-by Arrow implementations implement <a
href="https://arrow.apache.org/docs/format/Columnar.html#format-metadata-extension-types">extension
types</a> and can also be used to add
+by Arrow implementations to support <a
href="https://arrow.apache.org/docs/format/Columnar.html#format-metadata-extension-types">extension
types</a> and can also be used to add
use case-specific context to a column of values where the formality of an
extension type
is not required. In previous versions of DataFusion field metadata was
propagated through
certain operations (e.g., renaming or selecting a column) but was not
accessible to others
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@datafusion.apache.org
For additional commands, e-mail: commits-h...@datafusion.apache.org
