Styxis
Company
Knowledge

Iceberg expireSnapshots inside a transaction: check files before catalog commit

A successful maintenance call is less informative than whether still-published snapshots retain available file references.

Judge maintenance against published references

Maintenance approval should include file availability for still-published snapshots, not only a successful current-table query. Truthound can compare catalog references with an object inventory. It does not restore objects or control deletion order. [1, 2, 3]

Deletion before the transaction is public

The public Iceberg reproduction describes expireSnapshots inside a Java Transaction deleting files before the final catalog commit. If that commit fails or the process stops, the catalog can continue referencing files that are gone. A direct expire action and a transaction-local invocation must not be treated as the same execution path. [1]

Separate the plan, commit and observed objects

Compare file references from the approved catalog snapshot with an object inventory observed at the same point. Separate deletion plans whose commits are not confirmed. Record observation time and read permissions alongside snapshot identities and paths. An object hidden by insufficient permission is not automatically evidence of physical deletion. [1, 3]

An illustrative dangling-reference case

If every required path of a published snapshot exists in the inventory, a dangling-reference count of 0 passes. A missing required path producing a count of 1 fails. A latest-table read that happens to succeed does not excuse another published snapshot's failure. References whose expiration is confirmed belong outside the approved live scope. [1, 3]

The Truthound referential check

Truthound Core's ReferentialIntegrityValidator can check that snapshot paths exist in a prepared object-path inventory. Storage tooling is responsible for inventory consistency, permissions and completeness. On failure, hold further cleanup approval and investigate a supported path separating catalog commit from deletion. Passing this existence check does not establish that file contents are correct. [1, 2, 3]

Application conditions

Link referenced_path for an approved snapshot_id with the object_path inventory observed at the same point, recording permissions and observation time.

Alternatives

Use a supported maintenance path separating catalog commit from object deletion.

Limitations

  • Storage tooling owns inventory collection, permissions and consistency. Truthound neither deletes nor restores files.

Evidence

Event checked
Subject checked
Modified