Skip to content

Update Implementation Status to use Repo Names#105

Merged
wgtmac merged 1 commit into
apache:productionfrom
platypii:implementation-refactor
Mar 4, 2025
Merged

Update Implementation Status to use Repo Names#105
wgtmac merged 1 commit into
apache:productionfrom
platypii:implementation-refactor

Conversation

@platypii

@platypii platypii commented Mar 2, 2025

Copy link
Copy Markdown
Contributor

This PR updates the implementation status table in content/en/docs/File Format/implementationstatus.md to 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 have arrow, instead of Java, we now have parquet-java, and so on. From a practical point of view, most users will probably use parquet through pyarrow anyway 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.

@wgtmac

wgtmac commented Mar 3, 2025

Copy link
Copy Markdown
Member

@alamb WDYT?

@alamb

alamb commented Mar 3, 2025

Copy link
Copy Markdown
Collaborator

I think this is a great improvement in clarity -- thank you @platypii and @wgtmac for the ping

@wgtmac wgtmac merged commit be7f65c into apache:production Mar 4, 2025
@wgtmac

wgtmac commented Mar 4, 2025

Copy link
Copy Markdown
Member

I just merged it. Thanks @platypii and @alamb!

@platypii platypii deleted the implementation-refactor branch March 4, 2025 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants