Skip to content

feat(table): reject reserved metadata column IDs in user schemas#821

Draft
laskoviymishka wants to merge 1 commit intoapache:mainfrom
laskoviymishka:feat/reject-reserved-field-ids
Draft

feat(table): reject reserved metadata column IDs in user schemas#821
laskoviymishka wants to merge 1 commit intoapache:mainfrom
laskoviymishka:feat/reject-reserved-field-ids

Conversation

@laskoviymishka
Copy link
Copy Markdown
Contributor

Add validation in checkSchemaCompatibility to reject schemas that use reserved metadata column field IDs (2147483540 for _row_id, 2147483539 for _last_updated_sequence_number). These IDs are reserved by the Iceberg v3 spec for row lineage and must not be used by user-defined fields.

Together with #735 should close #727

Add validation in checkSchemaCompatibility to reject schemas that use
reserved metadata column field IDs (2147483540 for _row_id, 2147483539
for _last_updated_sequence_number). These IDs are reserved by the
Iceberg v3 spec for row lineage and must not be used by user-defined
fields.
@laskoviymishka laskoviymishka changed the title feat: reject reserved metadata column IDs in user schemas feat(table): reject reserved metadata column IDs in user schemas Mar 28, 2026
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.

feat: v3 support: Row lineage completion for v3 commits

1 participant