This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/datafusion.git
The following commit(s) were added to refs/heads/main by this push:
new dfe0f26b5f docs: add Supermetal to known users (#23790)
dfe0f26b5f is described below
commit dfe0f26b5f944c2ca7dfa748313f8eac00232775
Author: Kumar Ujjawal <[email protected]>
AuthorDate: Wed Jul 22 13:59:46 2026 +0530
docs: add Supermetal to known users (#23790)
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes #123` indicates that this PR will close issue #123.
-->
- Closes #.
## Rationale for this change
About Supermetal:
> Supermetal is a change data capture (CDC) platform that synchronizes
data between databases, data warehouses, and lakehouses while preserving
transactional consistency. It handles low latency streaming and large
scale batch movement with exceptional compute efficiency, replicating
terabytes on hardware as small as a 2 vCPU, 8GB instance.
> It ships as a single binary with no external dependencies and runs
anywhere, on premise, hybrid, or multi cloud.
<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->
## What changes are included in this PR?
Adds [Supermetal](https://supermetal.io/) (https://supermetal.io/), a
change data capture platform, to the list of known DataFusion users.
<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->
## Are these changes tested?
Yes
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->
## Are there any user-facing changes?
No
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
---
docs/source/user-guide/introduction.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/source/user-guide/introduction.md
b/docs/source/user-guide/introduction.md
index 20e9bf58b6..bf6809e1e9 100644
--- a/docs/source/user-guide/introduction.md
+++ b/docs/source/user-guide/introduction.md
@@ -133,6 +133,7 @@ Here are some active projects using DataFusion:
- [SedonaDB](https://github.com/apache/sedona-db) A single-node analytical
database engine with geospatial as a first-class citizen
- [Sleeper](https://github.com/gchq/sleeper) Serverless, cloud-native,
log-structured merge tree based, scalable key-value store
- [Spice.ai] Building blocks for data-driven AI applications
+- [Supermetal](https://supermetal.io/) is a change data capture (CDC) platform
that synchronizes data between databases, data warehouses, and lakehouses
- [Synnada] Streaming-first framework for data products
- [VegaFusion] Server-side acceleration for the
[Vega](https://vega.github.io/) visualization grammar
- [Vortex] An extensible, state of the art columnar file format
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
