-
Notifications
You must be signed in to change notification settings - Fork 6.7k
[Data] decrease parquet metadata storage usage #54821
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
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
4e5eb34
decrease parquet metadata storage usage
sword865 b1c9309
code format
sword865 2c0ffd3
Update python/ray/data/datasource/parquet_meta_provider.py
sword865 ed52615
google copilot import unneed code, remove it
sword865 51b698a
merge _dedupe_metadata and _dedupe_schemas
sword865 e016ea0
Merge branch 'master' into parquet_meta
sword865 16ef5ae
remove _dedupe_metadata for simplify
sword865 403bdd1
Merge remote-tracking branch 'github/parquet_meta' into parquet_meta
sword865 ae59f0a
Add comment
bveeramani 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 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
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.
Do we not want to dedupe metadata for this code path?
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.
Since the else branch handles only a single task that is already deduplicated in _fetch_metadata, there is no need to perform deduplication again (which is only required for multi-task scenarios).
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 see. Preference is to dedupe schemas in both branches to avoid making assumptions about the implementation, I'm not strongly opinionated on this
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.
This could introduce redundant computation, so I suggest avoiding it at this point in the
else
branch.