2 回答
- 最新
- 投票最多
- 评论最多
0
Tried it again and waited 48 hours, the records showed up. Perhaps more docs from AWS in this aspect can help.
已回答 2 年前
0
This might be an idempotency issue, did you check if the mapping for batch load / time granularity keeps the time+dimesions+measure/partition unique. As you describe it as a deterministic problem, that would be my first idea.
已回答 2 年前

The time, dimension, measure (no custom user defined partitions) are unique for the records that were dropped. In other words, there are no duplicate records with the same time, dimension and measure.
Is that what you meant?