S3 contains raw and processed objects with the same schema.
The Athena table must read only processed data and never accidentally include raw files.
Which configuration is most appropriate?
Set the catalog Table Location and each Partition Location to the intended S3 URIs.
Detailed explanation
Catalog metadata then points Athena at the intended physical data only.
Catalog metadata then points Athena at the intended physical data only.
An audit resource name is not necessarily the data prefix for the table.
An audit resource name is not necessarily the data prefix for the table.
A Region does not identify the correct raw or processed prefix.
A Region does not identify the correct raw or processed prefix.
A logical name does not change the S3 location that the query reads.
A logical name does not change the S3 location that the query reads.
Check official documentation
Compare the following points with the official documentation.
Glue Catalog StorageDescriptor.Location、partition location、Athena外部テーブルの公式説明を確認する。
What to confirm
論理名・リージョン・監査リソース名と物理データ場所を区別できる。
Key points
- Table Location
- Partition Location
- S3 URI
- Storage descriptor
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Logical versus physical
A table name is an identifier; the location determines which objects a query reads.
Boundary control
Separate raw, processed, and temporary prefixes to prevent accidental inclusion.