-
Notifications
You must be signed in to change notification settings - Fork 1.1k
docs: Add link to the Arrow implementation status page #8732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
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
martin-g
approved these changes
Oct 28, 2025
Member
|
unrelated: Should Avro be checked now for Rust at https://arrow.apache.org/docs/status.html#third-party-data-formats ? |
Member
|
mbrobbel
approved these changes
Oct 28, 2025
Co-authored-by: Matthijs Brobbel <m1brobbel@gmail.com>
Contributor
Author
|
I will also update other spec pages: |
etseidl
approved these changes
Oct 29, 2025
Contributor
Author
|
🚀 |
pull bot
pushed a commit
to thompson-tomo/arrow
that referenced
this pull request
Oct 31, 2025
…pache#47987) ### Rationale for this change - closes apache#47986 The Rust implementation has gained many features recently and it would be good to update the status page It turns out the Rust implementation is quite complete now 🎉 We are also consolidating our docs to point here as the canonical source of status. See - apache/arrow-rs#8732 ### What changes are included in this PR? Update the status page https://arrow.apache.org/docs/status.html to reflect the Rust implementation status I will comment inline with doc / code references ### Are these changes tested? ### Are there any user-facing changes? Doc only, no behavior changes * GitHub Issue: apache#47986
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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?
Rationale for this change
Let's help users know what features are supported by this crate
What changes are included in this PR?
Add a link to the arrow implementation status
Are these changes tested?
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?
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 call them out.