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 e16d453516 docs: add Streamling to known users (#24439)
e16d453516 is described below
commit e16d453516453bb01b4626df62ed36756ab376c9
Author: Yaroslav Tkachenko <[email protected]>
AuthorDate: Tue Aug 18 08:14:30 2026 +0000
docs: add Streamling to known users (#24439)
## 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.
-->
- N/A
## Rationale for this change
<!--
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.
Please explain the problem you are trying to solve in terms of the
user-visible
behavior, rather than the implementation.
For example, "The code in `foo.rs` doesn't handle nulls" is a symptom of
the
implementation. "COUNT(DISTINCT) returns wrong results when the column
contains
nulls" is the user-visible problem.
-->
## What changes are included in this PR?
<!--
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.
-->
Adding [Streamling](https://www.streamling.dev/) to the list of known
DataFusion users.
## Are these changes tested?
<!--
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)?
-->
Confirmed Markdown is correctly rendered.
## Are there any user-facing changes?
<!--
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.
-->
No.
---
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 1d9b618a01..d3c56630cf 100644
--- a/docs/source/user-guide/introduction.md
+++ b/docs/source/user-guide/introduction.md
@@ -135,6 +135,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
+- [Streamling](https://www.streamling.dev/) Data streaming runtime focused on
performance, consistency, and extensibility
- [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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
