Styxis
Company
Knowledge

Retain a shared Puffin file while any active deletion vector uses it

Retain a shared Puffin container when another active reference survives a deletion-vector replacement. Reconcile cleanup candidates with the full reference graph, then check offsets and contents separately.

Container lifetime follows all references

When deletion operates on a container file, its lifetime depends on every active deletion-vector reference inside it. Truthound Core can check prepared references against a physical inventory before retention work removes that container. [1, 2, 3]

One replaced vector in a shared file

Trino issue #31474 reports Iceberg v3 sharing one Puffin file between two deletion vectors. Replacing only one vector and expiring snapshots can remove the shared file still used by the other, causing a query failure in the reported reproduction. [1]

Use the current reference graph

Collect each data file’s current vector, Puffin path, and offset. Compare cleanup candidates with the complete active reference graph after one vector changes. Container-level cleanup cannot use the replacement of one member as evidence that every member is obsolete. [1, 3]

A moves while B still uses P

Let Puffin P hold DV-A and DV-B. Move only A to a new file; B still references P. Expected B-to-P resolution=true. true passes; false after deleting P fails because active delete information was removed. A file count cannot show which vector reference broke. [1, 3]

Presence differs from vector contents

ReferentialIntegrityValidator in Truthound Core Python SDK 3.3.2 compares an operator-prepared reference column with reference_data inventory. It checks presence, not DV offsets or contents. The SDK does not run expire_snapshots or reconstruct deleted vectors. [1, 2, 3]

Test shared and unshared retention

Test retention with shared and unshared vector files separately, checking all remaining references before approving the cleanup path. Preserve the post-change active graph rather than the graph from before A moved. [1, 3]

Follow presence with a real read

A retained P is a necessary condition for B, not proof that B points to the correct offset. Follow presence checks with the consumer read needed to verify that the deletion information still has the intended effect. [1, 3]

Application conditions

Extract the post-change active data-file/DV-offset/Puffin reference graph.

Alternatives

Verify shared/unshared retention tests and a real consumer read.

Limitations

  • Puffin presence does not establish DV offset or content correctness.

Evidence

Event checked
Subject checked
Modified