You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Glue] Support OpenTableFormatInput for Iceberg table creation #9705
The AWS Glue CreateTable API supports an optional OpenTableFormatInput parameter for creating Apache Iceberg tables. This parameter is currently ignored by moto.
AWS Documentation
CreateTable API - shows OpenTableFormatInput as an optional parameter
Hi @pomykalakyle! Is the OpenTableFormatInput actually exposed anywhere in the AWS API? I'm not seeing that parameter come back in any other operations (like get_table, where I would expect it).
Probably a related note: Moto (with a few exceptions) just mocks the AWS API, it doesn't actually expose a Iceberg table that you can connect to. The linked PR seems to try and execute SQL queries, and that will not work against Moto.
From what I've seen, when OpenTableFormatInput is used to create the table, the response for get_table would have information specific to Iceberg. (The columns in storage descriptor would have parameters such as iceberg.field.id. And the table parameter would have table_type of value iceberg.) Indeed, get_table does not return OpenTableFormatInput verbatim, so some knowledge of the Iceberg spec may be needed for creating the mock response.
I'm not sure about the efforts if we want to mock the get_table response with high fidelity. But Moto doesn't need to create an Iceberg table. As long as the table metadata is mocked in certain ways, the SQL engine would be able to use such information to work with the actual Iceberg table (e.g., a table stored in a mocked S3 service). It seems that Glue also creates Iceberg manifest files in the storage system (e.g., S3) according to the table location specified by OpenTableFormatInput. So this is more than simply mocking the response.
Activity
test: add partition transform tests for Iceberg and Glue catalogs
bblommers commentedon Feb 10, 2026
Hi @pomykalakyle! Is the
OpenTableFormatInputactually exposed anywhere in the AWS API? I'm not seeing that parameter come back in any other operations (likeget_table, where I would expect it).Probably a related note: Moto (with a few exceptions) just mocks the AWS API, it doesn't actually expose a Iceberg table that you can connect to. The linked PR seems to try and execute SQL queries, and that will not work against Moto.
linhr commentedon Mar 8, 2026
From what I've seen, when
OpenTableFormatInputis used to create the table, the response forget_tablewould have information specific to Iceberg. (The columns in storage descriptor would have parameters such asiceberg.field.id. And the table parameter would havetable_typeof valueiceberg.) Indeed,get_tabledoes not returnOpenTableFormatInputverbatim, so some knowledge of the Iceberg spec may be needed for creating the mock response.I'm not sure about the efforts if we want to mock theIt seems that Glue also creates Iceberg manifest files in the storage system (e.g., S3) according to the table location specified byget_tableresponse with high fidelity. But Moto doesn't need to create an Iceberg table. As long as the table metadata is mocked in certain ways, the SQL engine would be able to use such information to work with the actual Iceberg table (e.g., a table stored in a mocked S3 service).OpenTableFormatInput. So this is more than simply mocking the response.cc @pomykalakyle
feat: add OpenTableFormatInput support for Glue CreateTable
test: add partition transform tests for Iceberg and Glue catalogs