[SPARK] Add support for Parquet compression codec configuration in Delta tables#6802
Open
felipepessoto wants to merge 1 commit into
Open
[SPARK] Add support for Parquet compression codec configuration in Delta tables#6802felipepessoto wants to merge 1 commit into
felipepessoto wants to merge 1 commit into
Conversation
Signed-off-by: Felipe Fujiy Pessoto <fepessot@microsoft.com>
felipepessoto
changed the title
5 tasks
Contributor
Author
|
@emkornfield, @scottsand-db @scovich this PR address the #6324 (comment) |
Contributor
Author
|
@nicklan could you help review it, please? |
8 tasks
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
1 participant
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 Delta project/connector is this regarding?
Description
Add support for Parquet compression codec configuration in Delta tables
I haven't changed the default to ZSTD yet, I plan to do in a separate PR as I expect that changing the default might raise concerns.
Fix #6803
How was this patch tested?
Unit tests
Does this PR introduce any user-facing changes?
Exposes a new config, no behavior changes by default