-
Notifications
You must be signed in to change notification settings - Fork 431
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
Column/field description #447
Comments
For every column, you can store arbitrary key-value metadata (string -> string), see at parquet-format/src/main/thrift/parquet.thrift Line 809 in 5a5c894
|
Hello @gaborcsardi Yes, thanks for the tip but it can't be exploited by a software such as dataviz, etl or dataviz. |
Hi! I'm confused by different types of metadata.
column-level information and data types are recorded here. But how to you write something into THAT |
Since Parquet is now meant to be a standard file format, use for intermediate storage between tools, it really seems necessary to have this field/column description added. It exists in a lot of format such as Tableau Hyper, Alteryx yxdb, etc As for now, it means loosing informations when storing in Parquet. Best regards, Simon |
Why can't dataviz or etl software add the description as metadata? E.g. as a key called |
@gaborcsardi Because it means asking the user of ETL a key name and the user of the dataviz the key name. This means another place (a file, a mail, an issue...) where the users have to share the information "hey guys, I put the field description in the key label". But since in most ETL or dataviz tool, you don't have the ability to retrieve metadata by key, users of each tools have to ask the tool editor a way to retrieve a value by key description. The whole process isn't user friendly. Since it's a very common metadata and a lot of file format already have it, I think this is way better to have it in the file format specification. As of today, this is probably my main pain point with Parquet. Best regards, Simon |
Describe the enhancement requested
Hello,
I may have misunderstood or misread the documentation but I didn't find it. I would love to have a field/column description just like we have in databases :
Best regards,
Simon
Component(s)
No response
The text was updated successfully, but these errors were encountered: