Support Configuring Parquet Column Specific Options via SQL Statement Options #7463
Conversation
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
devinjdangelo
changed the title
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.
Which issue does this PR close?
Closes #7442
Rationale for this change
Extends syntax and allowed options for SQL statement options to configure parquet column level options (e.g. different compression for each column).
What changes are included in this PR?
Implements new parsing utils and options for parquet column specific options.
Are these changes tested?
Somewhat by existing tests, more tests needed.
Are there any user-facing changes?
Breaking change. Setting default parquet write settings are now suffixed with _default. E.g. "compression_default" since now "compression" expects column level settings.