dyno commented on issue #1092: URL: https://github.com/apache/iceberg/issues/1092#issuecomment-2814220662
> [@rdblue](https://github.com/rdblue) > > Hello. I'm leaving an inquiry because I want to understand the "hive.metastore.disallow.incompatible.col.type.changes" setting in detail. When I read the [document](https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.metastore.disallow.incompatible.col.type.changes), it was found to be related to the possibility of converting the data type of the column and compatibility. However, if you use `ALTER TABLE iceberg.iceberg_db.iceberg_table DROP COLUMN 'name'`, the same error occurs. If you delete a column here, the data related to that column will be removed from the table, which I think is separate from the compatibility issue of data type, and I wonder what it has to do with this setting. can I check the code related to this? run into same "DROP COLUMN" problem. ``` t( a STRING, b INT, c STRING, d INT ) USING ICEBERG LOCATION '<some s3 path>'; alter table t drop column c; ``` > An error occurred while calling o137.sql. > : org.apache.iceberg.exceptions.CommitStateUnknownException: InvalidOperationException(message:The following columns have types incompatible with the existing columns in their respective positions : > d) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
