-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Parameters removed when creating Iceberg Glue Tables #33370
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
terraform-provider-aws/internal/service/glue/catalog_table.go Lines 1094 to 1101 in 715dc15
|
This functionality has been released in v5.16.1 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.5.0
AWS Provider Version
5.16.0
Affected Resource(s)
aws_glue_catalog_table
Expected Behavior
When modifying existing Glue Table with Iceberg configuration enabled (open_table_format_input) provider should modify configuration of the table while persisting Parameters values for:
Actual Behavior
Parameters metadata_location and table_type are removed and the table is no longer usable as an Iceberg table.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
and setting location in storage_descriptor
2. Check that table incudes Parameters: metadata_location and table_type
3. Add/rename column in storage descriptor
4. Apply terraform
5. After successful apply table loses Parameters: metadata_location and table_type
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
#33157
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: