szymonorz opened a new issue, #16564: URL: https://github.com/apache/iceberg/issues/16564
### Query engine Trino version 481 ### Question Hi, recently I have been playing around with several implementations of REST Catalog and I noticed that not everybody follows the spec when it comes to `purgeRequested` flag in `RESTSessionCatalog#dropTable(SessionContext, TableIdentifier)`. This specifically affects how `unregister_table` procedure behaves in Trino which calls that `dropTable` method. For example Lakekeeper sets default value of `purgeRequested` to `true` meaning calling `unregisted_table` ,which by documentation and definition should only affect metadata and keep the data untouched, results in deleting data and can cause accidental data loss if someone migrated from one REST catalog implementation to another and expected the procedure the behave the same. As I'm fairly new to iceberg I would like to hear what the consensus is on that behaviour. Should the difference between purgeTable and dropTable be up to catalogs implementation? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
