-
Notifications
You must be signed in to change notification settings - Fork 36
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
First draft of docs about parquet format vs mr #53
Merged
wgtmac
merged 13 commits into
apache:production
from
vinooganesh:vinooganesh/addFormatVsMrDocs
May 15, 2024
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
d8ba2ab
first draft of docs about parquet format vs mr
vinooganesh f760a75
add reference implementations list + minor wording change
vinooganesh eb5eaaa
add duckdb
vinooganesh fab717b
Updating c++ link and adding a few others
vinooganesh 59e761c
remove the previous plan to split out mr and format into 2 doc pages
vinooganesh 95c76fd
updating language + apache impala
vinooganesh ce4b854
Update content/en/docs/Overview/_index.md
vinooganesh 1f32099
updating per latest CR comments
vinooganesh 8cea17e
parquet go listed twice
vinooganesh 0c1e0cf
additioanl CR changes
vinooganesh 1ef775d
remove the word reference
vinooganesh f99ac57
add description of 'mr'
vinooganesh 452fa66
Update content/en/docs/Overview/_index.md
vinooganesh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @tustvold @pitrou @emkornfield to see if we need to add well-known Parquet implementations in the arrow-rs and Apache Arrow C++ libraries at this moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would make sense to generally cover the
parquet-cpp
/arrow
situation as this is also leading sometimes to a bit of confusion. Theparquet
part of the Arrow repository is actually part of the Parquet PMC, but back in the past we decided to merge it into Arrow as the Parquet C++ community was a subset of the Arrow C++ community and all development happened in the context of Arrow C++/Python.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a list of the implementations that I'm aware of / that are referenced here below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it is crucial I added some more below. I think the discussion on the ML on how the parquet community views other implementations is something we should document when we come to a consensus.