Use one metadata snapshot before deleting a Doris packed slice
Build packed-slice deletion candidates from every page of formal, recycle, and temporary references at one snapshot. Absence in inventories captured at different times does not establish absence overall.
Do not combine separate absences
Absence observed at two different times cannot be combined into proof of total absence. Truthound Core can check a prepared deletion plan against retained rowset references only after the operator collects them in one metadata snapshot. [1, 2, 3]
A formal-to-recycle interleaving
Doris issue #69861 describes recycle/tmp and formal-rowset reads using different transactions while compaction moves a rowset. Follow-up source inspection supports the interleaving but does not report an executed missing-data incident. Physical deletion also depends on correction eligibility and the packed file’s remaining references. [1]
Cover every page in one snapshot
Collect recycle, tmp, and every page of formal rowset state in one snapshot for each slice. Cross-check deletion candidates against unexpired references. Independent snapshots hidden behind one wrapper still do not make the absence decision coherent. [1, 3]
An unexpired recycle reference
Define an illustrative rowset with an existing recycle key and unexpired retention in the same snapshot. Its expected deleted flag is false. false passes; true fails even if no formal key remains, because the recycle reference still protects the slice. [1, 3]
Apply conditions to prepared state
ConditionalExpressionValidator in Truthound Core Python SDK 3.3.2 can apply a prepared retained-reference condition to the deletion flag. Snapshot collection and retention semantics come from the operator. The SDK does not open a metadata transaction or recover removed packed files. [1, 2, 3]
Validate before cleanup
Pause cleanup for affected slices until consistent state collection is verified, including old-reader references and multi-page scans. Other live slices may postpone physical object deletion without making an incorrect slice classification safe. [1, 3]
Later inventories are insufficient
The meaningful artifact is the reference decision at one point in time, not three later inventories. Matching that contract protects the planned operation while leaving writer atomicity and actual object recovery to the storage system. [1, 3]
Application conditions
Extract recycle/tmp and every formal page in one snapshot.
Alternatives
Pause cleanup for affected slices until consistent collection is verified.
Limitations
Inventories from separate times do not establish the race or a coherent absence decision.
Evidence
- Event checked
- Subject checked
- Modified
