- Newest
- Most votes
- Most comments
When working with S3 Tables (Iceberg format) in Athena, there are specific considerations for data types. The error you're encountering when trying to add an array<bigint> column is likely due to a mismatch between Athena's data type representation and Iceberg's underlying type system.
For Iceberg tables in Athena, there is a mapping between Athena data types and Iceberg data types. The Iceberg type list<E> maps to Athena's array type. Similarly, Iceberg's long type maps to Athena's bigint type.
When you're trying to create an array of bigint values, you should be able to use the array<bigint> syntax. However, there might be an issue with how this specific operation is handled for S3 Tables.
One thing to check is that your table and column names are all lowercase. S3 Tables require lowercase names for tables and columns to be properly supported by AWS Lake Formation and the AWS Glue Data Catalog. If your table definition contains capital letters, you might encounter errors.
Another consideration is that you might need specific permissions in Lake Formation to perform this operation. S3 Tables integrate with AWS Lake Formation for access control, and insufficient permissions could cause operations to fail.
If you continue to experience issues, you might want to try creating a new table with the array column included in the initial definition rather than adding it later, as some schema evolution operations might have limitations.
Sources
Query Apache Iceberg tables - Amazon Athena
Supported data types for Iceberg tables in Athena - Amazon Athena
Querying Amazon S3 tables with Athena - Amazon Simple Storage Service
S3 Tables - Unable to query using Athena | AWS re:Post
answered a year ago
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
