2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Tried it again and waited 48 hours, the records showed up. Perhaps more docs from AWS in this aspect can help.
répondu il y a 2 ans
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.
répondu il y a 2 ans
Contenus pertinents
- demandé il y a 3 ans
- demandé il y a 9 mois
- demandé il y a 9 mois
- AWS OFFICIELA mis à jour il y a 4 ans

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?