felixschneider99 opened a new issue, #14743: URL: https://github.com/apache/iceberg/issues/14743
### Apache Iceberg version 1.10.0 (latest release) ### Query engine Spark ### Please describe the bug 🐞 ### Description When executing: `DROP TABLE <table> PURGE;` with Iceberg + Spark, no purge operation is triggered. Instead, SparkCatalog always issues a standard dropTable request without purge. The **PURGE** keyword in Spark SQL has no effect. ### Relevant Code In the following **purgeTable()** method: https://github.com/apache/iceberg/blob/b35c7ec1b03e3897da68960cd556d635b2f5ae54/spark/v3.5/spark/src/main/java/org/apache/iceberg/spark/SparkCatalog.java#L369-L402 **dropTableWithoutPurging()** is always invoked: As a result, purge=true has no effect even though Spark SQL supports the PURGE keyword. ### Expected Behavior When running: `DROP TABLE my_table PURGE;` via Spark SQL, the SparkCatalog should trigger and actual purge operation. ### Question What is the reason that SparkCatalog always calls dropTableWithoutPurging() even when purge=true? If this behavior is by design, clarification or documentation would be appreciated — but the current implementation appears to be a bug. ### Willingness to contribute - [ ] I can contribute a fix for this bug independently - [x] I would be willing to contribute a fix for this bug with guidance from the Iceberg community - [ ] I cannot contribute a fix for this bug 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: [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]
