pvary commented on PR #13497: URL: https://github.com/apache/iceberg/pull/13497#issuecomment-3113821645
> > > we think the same sql should be same result in diffent engine, otherwise it leave other problems , such as ,leave many empty directory , leave orphan datafiles if user don't use purge. it will Increase unnecessary remedial work > > > > > > I think the 1st order of compatibility is for the engines themselves. The `DROP TABLE` should work the same way for Hive/Iceberg/Trino tables in Spark. The 2nd order of compatibility is between the engines, but the precedence is in engine behavior. > > but in spark3.5, iceberg table and non iceberg `drop table ` not same behavior when `external.table.purge=true` Is it possible to fix this behavioral difference in the Spark side? -- 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
