A new optional column is added to an event schema.
Keep downstream processing compatible and compare the schema before and after the change.
Which approach is most appropriate?
Use Glue Catalog table versions and review schema changes rather than deleting and recreating the table.
Detailed explanation
The actor may be known, but the table definition and schema version cannot be reconstructed.
The actor may be known, but the table definition and schema version cannot be reconstructed.
Table versions preserve metadata history for comparison, compatibility checks, and rollback decisions.
Table versions preserve metadata history for comparison, compatibility checks, and rollback decisions.
This loses history and can break dependent queries and jobs.
This loses history and can break dependent queries and jobs.
An object timestamp does not describe column or type changes.
An object timestamp does not describe column or type changes.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Catalog TableVersion、UpdateTable、Schema Registryの公式説明を確認する。
What to confirm
ファイル更新時刻・監査主体と、スキーマ版管理を区別できる。
Key points
- TableVersion
- Schema change
- Compatibility
- Rollback
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
History before replacement
Versioned metadata supports comparison and safer change review than delete and recreate.
Consumer impact
Check required columns, types, partitions, and downstream dependencies before promotion.