The GitHub Actions job "Java CI" on iceberg.git/fix/explicit-purge-false-parameter has succeeded. Run started by GitHub user hackintoshrao (triggered by hackintoshrao).
Head commit for run: d9e47f738d9f10b2216832e83b91061a90a4ee20 / Karthic Rao <[email protected]> REST: Explicitly send purgeRequested=false when dropping table without purge The REST catalog client previously omitted the purgeRequested parameter when calling dropTable with purge=false. This relied on the server defaulting to purge=false. However, some catalogs (e.g., MinIO AIStor) default purgeRequested to true to work around Spark's bug where it doesn't forward purgeRequested=true even when DROP TABLE ... PURGE is used. With those catalogs, calling dropTable(identifier, false) would unexpectedly purge the table data because the parameter was omitted and the server defaulted to true. This change explicitly sends purgeRequested=false to ensure the client's intent is honored regardless of the server's default behavior. Relates to: https://github.com/apache/iceberg/issues/11023 Report URL: https://github.com/apache/iceberg/actions/runs/21437693472 With regards, GitHub Actions via GitBox
