c-thiel opened a new issue, #11754: URL: https://github.com/apache/iceberg/issues/11754
### Feature Request / Improvement Currently when purge-dropping tables with Spark and the REST Catalog, Spark deletes all files of the tables before sending the drop request to the REST Catalog. In REST Catalog scenarios, we want the server to perform the drop. This enables scenarios like soft-deletion / undrop without leveraging the S3-only `s3.delete-enabled`. Thus the client shouldn't delete the files and communicate its intent to the server. As a temporary workaround a new flag is added in https://github.com/apache/iceberg/pull/11317. Long term a behavior change of DROP is desirable, which should happen in Iceberg Version 2. Discussed in the [Iceberg Catalog Sync](https://docs.google.com/document/d/1iPGVCIcr-M0XtAiudOguWAvmqIdVgpYN5vz5ohO8PKw/edit?tab=t.0#heading=h.hr54kssvr08w) of Dec. 11th. @RussellSpitzer could you add the 2.0 Milestone? Feel free to make it more precise as you see fit! ### Query engine None ### Willingness to contribute - [ ] I can contribute this improvement/feature independently - [ ] I would be willing to contribute this improvement/feature with guidance from the Iceberg community - [ ] I cannot contribute this improvement/feature at this time -- 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.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
