Add an optional attribute to an Apache Iceberg table on S3.
Keep existing snapshots and continue querying older data.
Which approach is most appropriate?
Use Iceberg schema evolution and snapshot management rather than overwriting every Parquet file directly.
Detailed explanation
Direct rewrites lose history and increase concurrent-update and reprocessing risk.
Direct rewrites lose history and increase concurrent-update and reprocessing risk.
Metadata can add the column while preserving table history and compatibility.
Metadata can add the column while preserving table history and compatibility.
A crawler infers catalog metadata but does not replace Iceberg snapshot recovery.
A crawler infers catalog metadata but does not replace Iceberg snapshot recovery.
TTL deletes DynamoDB items and cannot alter an S3 table schema.
TTL deletes DynamoDB items and cannot alter an S3 table schema.
Check official documentation
Compare the following points with the official documentation.
Apache Iceberg schema evolution、snapshots、AWS Glue Iceberg integrationの公式説明を確認する。
What to confirm
Icebergのメタデータによる列追加と、単純なファイル上書きの違いを説明できる。
Key points
- Apache Iceberg
- Schema evolution
- Snapshot
- Time travel
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Compatible addition
An optional column can be additive, while type changes may require a migration plan.
History management
Snapshot retention and concurrent commits support reproducible analysis and recovery.