1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Assuming the files have a consistent schema, is possible that the sample the crawler takes confuses it and is not able to resolve the conflict.
A simple solution that comes to mind is setting the right schema in the table and then configure the crawler to just add new partitions without touching the schema.

Thank you for taking your time towards this. Since I'm new to this crawler and schema. Could you share any document to follow the steps
Hi @Gonzaloherreros i have tried creating a new table without crawler first. with below given details https://github.com/aws-solutions/aws-waf-security-automations/blob/main/deployment/aws-waf-security-automations-firehose-athena.template line 179. then i created a new crawler to pull the data. which resulted in the same error with the other three fields requestbodysize, labels, requestbodyinspectedbywaf.
are you sure you set the crawler to just add partitions without updating the shema? the error should have changed