tanmayrauth commented on issue #1092:
URL: https://github.com/apache/iceberg-go/issues/1092#issuecomment-4488640111
Thanks for the question! A couple of notes on where we stand:
- For the REST catalog (by far the most common production path), purge is
already supported, the server handles physical deletion when
purgeRequested=true is sent. This is implemented today.
- For client-side catalogs (Glue, Hive, Hadoop), a client-side purge is
inherently best-effort, even Java's implementation can leave orphan files on
partial failure. Production deployments rely on expire-snapshots +
remove-orphan-files for reliable cleanup regardless.
We'd accept a PR that wires up client-side purge for non-REST catalogs (as
an optional interface), but it's not high priority since the reliable cleanup
path is through the maintenance operations. If you'd like to contribute it,
happy to review, just keep in mind it should be clearly documented as
best-effort.
@zeroshade @laskoviymishka what are your thoughts one this?
--
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]
