Event data is stored in S3 partitions by date.
A date-range Athena query should avoid reading files outside the requested range.
Which approach is most appropriate?
Filter on the registered partition column and select only needed columns so Athena can prune unrelated data.
Detailed explanation
Replicating audit logs does not optimize the event-table scan.
Replicating audit logs does not optimize the event-table scan.
File-name length does not determine partition pruning.
File-name length does not determine partition pruning.
Partition pruning skips dates that cannot satisfy the predicate.
Partition pruning skips dates that cannot satisfy the predicate.
Reading unnecessary columns increases scanned bytes and cost.
Reading unnecessary columns increases scanned bytes and cost.
Check official documentation
Compare the following points with the official documentation.
Amazon Athena partition pruning、partition projection、data scanの公式説明を確認する。
What to confirm
パーティション条件とSELECT *のスキャン量の違いを説明できる。
Key points
- Partition pruning
- WHERE clause
- Data scan
- Athena
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Cost and performance
Scan charges and latency depend on data read, so select columns and partitions deliberately.
Partition granularity
Use commonly filtered dimensions without creating excessive small partitions.