1 Answer
- Newest
- Most votes
- Most comments
0
I found the issue.
There was a job that was recreating the tables during deploys. MSCK REPAIR TABLE was being run after recreate, but it was not fully qualifying the database.tablename, so it was not discovering the existing partitions.
Edited by: lettermuckoo on Dec 18, 2019 1:56 PM
answered 4 years ago
Relevant content
- asked a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 months ago