Skip to content

fix(glue): Exclude historical schemas from Glue columns#2788

Open
VABVAT wants to merge 3 commits into
apache:mainfrom
VABVAT:fx/glue_duplicate_columns
Open

fix(glue): Exclude historical schemas from Glue columns#2788
VABVAT wants to merge 3 commits into
apache:mainfrom
VABVAT:fx/glue_duplicate_columns

Conversation

@VABVAT

@VABVAT VABVAT commented Jul 8, 2026

Copy link
Copy Markdown

Which issue does this PR close?

What changes are included in this PR?

This PR updates Glue schema conversion so AWS Glue StorageDescriptor.columns is populated only from the current Iceberg schema.

Previously, GlueSchemaBuilder::from_iceberg converted the current schema and then also converted historical schemas from table metadata. Those historical fields were written to Glue with iceberg.field.current=false, but Glue does not use that parameter to filter visible columns, which could cause duplicate columns to appear in the Glue Console after schema evolution.

Historical schemas are still preserved in Iceberg table metadata. This change only prevents them from being projected into Glue's visible column list.

Are these changes tested?

Yes.

Added a regression test covering schema evolution with historical schemas, and verified the Glue schema output contains only current schema fields.

Ran locally:

cargo test -p iceberg-catalog-glue

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.

iceberg-catalog-glue pushes all historical schema fields to Glue, causing duplicate columns in Glue UI

1 participant