marton-bod opened a new pull request #2191: URL: https://github.com/apache/iceberg/pull/2191
There are a couple of scenarios where the Hive DDL command `DROP TABLE` can produce an error unnecessarily. 1. Currently on Hive4, DROP TABLE can result in a `FileNotFoundException` exception, because based on Hive2/Hive3 behaviour, the current assumption is that the `HiveIcebergMetaHook` has to clean up the metadata files after the Hive drop table has completed. However, in Hive4, if `external.table.purge=TRUE` is set, Hive will wipe the metadata folder as well. 2. When creating a Hive table on top of an existing table in a different catalog, if we drop the table in Hive but the underlying table does not exist anymore (e.g. in the HadoopCatalog), we'd also end up with an exception. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
