Skip to content

GH-563: Make ColumnMetaData.path_in_schema optional #564

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.

Sign up for GitHub

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

Open
etseidl wants to merge 3 commits into
base: master
Choose a base branch
from
Open

GH-563: Make ColumnMetaData.path_in_schema optional #564

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bb5e7cf
make ColumnMetaData.path_in_schema optional
etseidl Apr 8, 2026
3164061
Update src/main/thrift/parquet.thrift
etseidl Apr 10, 2026
79c18dd
pick a date after which writers can default to omitting field
etseidl Apr 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions src/main/thrift/parquet.thrift
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -885,8 +885,17 @@ struct ColumnMetaData {
* whether we can decode those pages. **/
2: required list<Encoding> encodings

/** Path in schema **/
3: required list<string> path_in_schema
/**
* Path in schema
*
* The writing of this field has been made optional as of version 2.X.0.
Comment thread
etseidl marked this conversation as resolved.
Outdated
* The information contained in this field is easily obtainable from
* the schema, and redundantly storing it here can lead to unnecessary
* bloat in the footer. Writers are encouraged to make the writing of
* this field optional, but for maximal compatibility should default to
* writing the field until at least Month 202X.
Copy link
Copy Markdown
Contributor

@emkornfield emkornfield Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on "Forward incompatible features/changes should not be turned on by default until 2 years after the parquet-java implementation containing the feature is released." Lets maybe fill in the date as September 2028, assuming we get things merged by a september java release?

Copy link
Copy Markdown
Contributor Author

@etseidl etseidl Apr 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've gone ahead and put Sept 2028 in the text for now. We can update as needed later.

*/
3: optional list<string> path_in_schema

/** Compression codec **/
4: required CompressionCodec codec
Expand Down