REST: Explicitly send purgeRequested=false when dropping table without purge

[hackintoshrao]

Summary

Modify RESTSessionCatalog.dropTable() to explicitly send purgeRequested=false instead of omitting the parameter.

Problem

Currently, dropTable(context, identifier) sends a DELETE request without the purgeRequested parameter, relying on the server to default to false.

However, some catalogs default purgeRequested=true to work around Spark's bug where it doesn't forward purgeRequested=true even with DROP TABLE ... PURGE (#11023, #11317).

With such catalogs, calling catalog.dropTable(identifier, false) unexpectedly purges table data because the parameter is omitted and the server defaults to true.

Solution

Explicitly send purgeRequested=false:

client.delete(
    paths.table(identifier),
    ImmutableMap.of("purgeRequested", "false"),
    ...);

This ensures the client's intent is honored regardless of server defaults.

Related Issues

• deletion & purge improvements for undelete feature in REST catalog #11023 - deletion & purge improvements for undelete feature in REST catalog
• Spark: add property to disable client-side purging in spark #11317 - Spark: add property to disable client-side purging in spark

[github-actions]

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions.

[github-actions]

This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.