Skip to content

GH-421: Clarify schema field name uniqueness - #610

Draft
d33bs wants to merge 1 commit into
apache:masterfrom
d33bs:cols-same-name
Draft

GH-421: Clarify schema field name uniqueness#610
d33bs wants to merge 1 commit into
apache:masterfrom
d33bs:cols-same-name

Conversation

@d33bs

@d33bs d33bs commented Aug 22, 2026

Copy link
Copy Markdown

Rationale for this change

The Parquet format did not say whether two sibling fields can have the same name. This can make path_in_schema ambiguous, because one path can match more than one field.

What changes are included in this PR?

This PR updates the Thrift schema comments to state that direct children of a group must have distinct names. Name comparison is case-sensitive.

It also clarifies that path_in_schema must identify exactly one primitive field.

Do these changes have PoC implementations?

No. This is a specification clarification only.

Closes #421

State that sibling fields in a schema group must have distinct names.

Clarify that path_in_schema must identify one primitive field.

Closes apache#421.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The Parquet Spec doesn't specify whether multiple columns are allowed to have the same name.

1 participant