Repository navigation
docs: Clarify Known Users criteria and clean up active project list - #26926
Merged
Merged
Conversation
- Visible criteria and use-evidence rule added. - Eight entries moved; canonical links fixed. - Public repositories re-audited.
- Inlined 33 links in the user guide introduction. - Removed 25 URL definitions from the documentation. - Preserved the invitation text in the updated guide.
kosiew
marked this pull request as ready for review
October 30, 2026 11:26
kumarUjjawal
left a comment
Contributor
There was a problem hiding this comment.
Thank you @kosiew
This looks like a nice improvement to me.
kumarUjjawal
approved these changes
Oct 31, 2026
alamb
approved these changes
Nov 2, 2026
alamb
left a comment
Contributor
There was a problem hiding this comment.
Thank you @kosiew and @kumarUjjawal
- Expand Apache references, eg Apache Auron - Expand Cloudflare reference
- Replaced HoraeDB with OpenObserve in Use Cases. - Added Cloudflare R2 Query Engine with deep-dive link.
Contributor
Author
|
🚀 |
kosiew
enabled auto-merge
November 3, 2026 02:55
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 3, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 3, 2026
This was referenced Nov 3, 2026
Closed
Phoenix500526
pushed a commit
to Phoenix500526/datafusion
that referenced
this pull request
Nov 3, 2026
…sh_collisions (apache#27034) ## Which issue does this PR close? - Closes apache#27033. ## Rationale for this change `completed_groups_release_first_value_bitmap` (added in apache#26782) takes about 10 minutes in the `cargo test hash collisions (amd64)` merge-queue job. It aggregates 131,072 distinct keys in one batch. Under `force_hash_collisions`, every key has the hash 0, so the aggregate is quadratic. The test checks that `FIRST_VALUE(v ORDER BY v)` releases its per-batch bitmap, which does not depend on hashing. The long job gives spot runner shutdowns more time to hit it. Evidence from merge-queue runs: - In the passing rerun for apache#26926 ([job](https://github.com/apache/datafusion/actions/runs/41571721394/job/125710730373)), the physical-plan unit test binary took 609.89s. All other tests in it finished by 03:40:31. This test ran from about 03:40:07 to 03:50:17. - The median job time went from 6.2 minutes (230 jobs, Oct 21 to Oct 30) to 12.0 minutes (70 jobs after apache#26782 merged). - All 5 failed attempts of the job since then were runner shutdowns while this test was running: apache#26929 ([job](https://github.com/apache/datafusion/actions/runs/41114163010/job/124263887540)), apache#26898 ([job](https://github.com/apache/datafusion/actions/runs/41115099549/job/124267135386)), apache#26883 ([job](https://github.com/apache/datafusion/actions/runs/41120437208/job/124285496814)), apache#26974 ([job](https://github.com/apache/datafusion/actions/runs/41559552415/job/125666576696)), apache#26926 ([job](https://github.com/apache/datafusion/actions/runs/41571721394/job/125705896210)). ## What changes are included in this PR? Skip the test under `force_hash_collisions`, as apache#26594 did for another test. The imports that only this test uses move into its body, so they are not unused under the feature. ## What is the testing strategy for this PR? Test config change only. The regular `cargo test` job still runs the test. Locally (`--profile ci`), the test takes 0.92s by default and 309s with `force_hash_collisions`. With the feature, it is now skipped, and Clippy passes with and without the feature. ## Are there any user-facing changes? No.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #26803.
Rationale for this change
The "Known Users" section previously defined an active project using only a six-month commit activity criterion, documented in an HTML comment rather than visible to readers.
This made inclusion requirements unclear and allowed inactive or minimally adopted projects to remain in the active list. Some entries also contained outdated repository links.
This PR establishes visible, measurable inclusion criteria and reorganizes the list to better distinguish active projects from other projects using or having used DataFusion.
What changes are included in this PR?
What is the testing strategy for this PR?
Documentation-only change. No automated tests are added or modified in this patch.
The changes can be reviewed by inspecting the Markdown, checking the updated links, and verifying project placement against the documented inclusion criteria.
Are there any user-facing changes?
Yes. Readers of the DataFusion user guide will see explicit inclusion criteria for the Known Users active list, an updated classification of projects, and corrected or additional project references.
There are no changes to DataFusion runtime behavior or public APIs.
LLM-generated code disclosure
This PR includes LLM-generated code and comments. All LLM-generated content has been manually reviewed.