Update Implementation Status to use Repo Names#105
Merged
Conversation
Member
|
@alamb WDYT? |
Collaborator
wgtmac
approved these changes
Mar 4, 2025
Member
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.
This PR updates the implementation status table in
content/en/docs/File Format/implementationstatus.mdto use the repository names instead of the language. This is because the repository name is more specific than the language, and this handles the case where there are multiple implementations in the same language.So for example, instead of
C++, we now havearrow, instead ofJava, we now haveparquet-java, and so on. From a practical point of view, most users will probably use parquet throughpyarrowanyway so maybe this will make it easier for users to understand which libraries support which features.I added the language in parentheses after the repository name to help users choose a library in their preferred language.
Note: Stylistically I considered using unicode characters 🇷 and 🇼 to indicate read and write support per @wgtmac's suggestion in #102. But different browsers and operating systems render these characters differently, often different size and style from the existing checkmark (✅) and cross (❌) characters. I decided to stick with the existing characters for consistency.