JSON events may gain optional columns, but existing column types must not change.
Prevent a crawler from applying an incompatible update to the existing table.
Which configuration is most appropriate?
Configure the crawler SchemaChangePolicy and classifiers to control how additions and incompatible changes are handled.
Detailed explanation
Authorization can restrict API calls but cannot judge semantic schema compatibility.
Authorization can restrict API calls but cannot judge semantic schema compatibility.
An object timestamp is not a policy for schema type changes.
An object timestamp is not a policy for schema type changes.
Recreation loses operational history and does not validate compatibility.
Recreation loses operational history and does not validate compatibility.
The crawler's update and delete behavior can be constrained so incompatible changes are not applied silently.
The crawler's update and delete behavior can be constrained so incompatible changes are not applied silently.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Crawler SchemaChangePolicy、UpdateBehavior、DeleteBehaviorの公式説明を確認する。
What to confirm
メタデータ更新ポリシーとIAM権限の役割を区別できる。
Key points
- SchemaChangePolicy
- UpdateBehavior
- DeleteBehavior
- Classifier
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Compatibility boundary
Authorization can restrict an API call, but it cannot decide whether a new type is safe for consumers.
Safe discovery
Review inferred types and use explicit contracts when crawler inference is not sufficient.