- Newest
- Most votes
- Most comments
The error you're encountering, "ICEBERG_BAD_DATA: Multiple entries with same key: 20=data.account.acid and 20=acid", suggests an issue with duplicate keys in your Iceberg table data. This problem typically occurs when there are inconsistencies in the table's metadata or data files.
To resolve this issue, you can try the following steps:
-
Verify the table's schema and ensure that there are no duplicate column names or conflicting data types.
-
Check if there have been any recent changes or updates to the table that might have introduced inconsistencies.
-
Consider running a table repair or optimization operation if available for Iceberg tables in Athena.
-
If the issue persists, you may need to recreate the table with clean data, ensuring that there are no duplicate keys in the process.
-
If you're using partitioned tables, verify that the partitioning is correct and there are no overlapping or duplicate partition keys.
If these steps don't resolve the issue, it may be necessary to investigate the underlying data files and metadata more closely. In some cases, you might need to reach out to AWS Support for further assistance, providing them with the specific query ID and details about your table structure and recent operations performed on it.
Sources
Troubleshoot Athena Apache Iceberg table errors | AWS re:Post
Athena : TYPE_NOT_FOUND: Unknown type: row | AWS re:Post
Relevant content
- asked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago