Require Iceberg v2 snapshot fields beyond one reader’s acceptance
Check required fields for the Iceberg format version separately from reader acceptance. Verify manifest-list and summary presence in a new snapshot before proceeding to the contents of its references.
One reader is not the format contract
A metadata format’s required fields need explicit checks even if one implementation accepts the file. Truthound Core can inspect an extracted version-and-field table before cross-reader compatibility is approved. [1, 2, 3]
Java and PyIceberg differ
Iceberg issue #18646 reports the main development builder accepting a v2 snapshot with manifests but no manifest-list. Java loads it while PyIceberg 0.12 reports a required-field error. Other format-version requirements in the issue are distinct checks, not evidence that this field pair certifies all metadata. [1]
Apply the new metadata’s version
Extract format-version, snapshot ID, manifest-list presence, and summary presence. Apply the version-specific contract to new metadata. Keep reader load outcomes separately so permissive acceptance cannot erase a missing required field. [1, 3]
The two-presence conjunction
Define the illustrative v2 contract as requiring both manifest-list and summary. Their combined presence=true passes. false fails the two-field requirement even if Java accepts the metadata. This Boolean does not examine manifest contents or row-ID allocation. [1, 3]
Inspect prepared snapshot summaries
RowLevelValidator in Truthound Core Python SDK 3.3.2 can apply an operator-defined predicate to each extracted snapshot record. The operator supplies version semantics and presence extraction. The SDK does not fix the Iceberg builder or implement the metadata parser. [1, 2, 3]
Load through real consumers
Add compatibility loads for every real consuming implementation and retain version-specific writer checks. A successful Java load is one control, not a substitute for the independent format obligation. [1, 3]
Further validity remains separate
Treat field presence as an early acceptance boundary. Encryption, row ranges, actual manifest references, and snapshot semantics still need their own evidence after that boundary passes. [1, 3]
Application conditions
Extract snapshot format-version and actual manifest-list/summary presence.
Alternatives
Add real-consumer loads and version-specific writer checks.
Limitations
Field presence does not guarantee manifest contents, encryption, or row-range correctness.
Evidence
- Event checked
- Subject checked
- Modified
