Skip to content

Support for Iceberg Table Version 3 in Glue Data Catalog CreateTable API

0

Currently, when attempting to provision an Apache Iceberg table using the CreateTable API with version=3 inside the IcebergInput object, the API returns a 400 Bad Request error.

Error message received: InvalidInputException: Only creating iceberg table version 1 & 2 is supported

Because of this upstream API limitation, Infrastructure as Code tools are currently blocked from supporting Iceberg V3 table creation natively. I recently raised this with the HashiCorp team, and you can see the community impact and discussion in this Terraform AWS Provider issue: https://github.com/hashicorp/terraform-provider-aws/issues/46948

As the Apache Iceberg V3 specification brings important features, and engines like Amazon Athena and EMR are increasingly supporting V3, it is critical for us to be able to provision V3 tables natively via the API.

Could you please add this feature request to the product team's backlog to update the CreateTable and UpdateTable APIs to accept version=3 for Iceberg tables?

Thank you,

Fabrício

asked 2 months ago133 views
1 Answer
1

Thank you for reaching out about Iceberg table version 3 support in AWS Glue Data Catalog. I understand your need to provision Apache Iceberg V3 tables through the CreateTable API for Infrastructure as Code workflows.

Based on the current AWS Glue documentation, the CreateTable API's IcebergInput structure supports a Version parameter that defaults to version 2, and the valid values are currently limited to versions 1 and 2. This aligns with the error message you're receiving when attempting to create a version 3 table.

I appreciate you sharing the context about the Terraform provider limitation and the broader community impact. While I can confirm the current API limitation you've encountered, I'm not able to directly add items to the product team's backlog or provide timelines for feature releases.

To formally submit this as a feature request and ensure it reaches the appropriate AWS Glue product team, I recommend:

  1. Opening a support case through AWS Support if you have a support plan, which provides a direct channel to the service team
  2. Providing feedback through the AWS Glue console feedback mechanism
  3. Working with your AWS account team or Technical Account Manager if you have one, as they can advocate for feature requests on your behalf

These channels will ensure your request is properly tracked and considered for future releases. The product team evaluates feature requests based on customer demand and use cases like yours, so providing detailed context about your requirements and the impact on your workflows is valuable.

Thank you for taking the time to provide this feedback about Iceberg V3 support.
Sources
IcebergInput - AWS Glue
Table API - AWS Glue
CreateIcebergTableInput - AWS Glue

answered 2 months ago
EXPERT
reviewed 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.