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.
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
Allow adding user defined metadata to
ParquetSink
#10224Allow adding user defined metadata to
ParquetSink
#10224Changes from 5 commits
7b33bc8
86bf317
c35b326
cd91a77
0cf04b5
5b06bf3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 is quite and I missed it the first time around -- nice eyes @devinjdangelo . @wiedld could you please add documentation to the
TableParquetOptions
that documents this behavior?Specifically, I would be interested to know "what if you want to store metadata values that have spaces in them" (
key1:my value with spaces
)?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.
BTW it would be fine if the answer is "you will get an error / is not supported yet" -- it might just be good to document that behavior
I could see wanting to support things like
key1:"my awesome value" key2:"my other awesome value"
(again not in this PR, but we should at least document how it works I think)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.
Perhaps we could leverage a syntax like:
(
'format.metadata.key1' 'val1',
'format.metadata.key2' 'val2 with space',
...
)
to support values with spaces
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.
😆 You beat me to it.
I started with the internal double quotes approach, also considered escaped spaces; then I realized that these are introducing lexical rules which did not feel SQL appropriate. Landed on the approach suggested by @devinjdangelo , commit will be up shortly.