1 回答
- 最新
- 投票最多
- 评论最多
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
已回答 4 年前
相关内容
- AWS 官方已更新 3 年前
- AWS 官方已更新 2 年前