You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "rdblue (via GitHub)" <gi...@apache.org> on 2026/08/14 20:01:12 UTC
Re: [PR] Spec: Clarify content file uniqueness within a snapshot [iceberg]
rdblue commented on code in PR #17198:
URL: https://github.com/apache/iceberg/pull/17198#discussion_r3786792694
##########
format/spec.md:
##########
@@ -674,11 +674,13 @@ A manifest file must store the partition spec and other metadata as properties i
| _optional_ | _required_ | `format-version` | Table format version number of the manifest as a string |
| | _required_ | `content` | Type of content files tracked by the manifest: "data" or "deletes" |
-The schema of a manifest file is defined by the `manifest_entry` struct, described in the following section.
+#### Content file uniqueness
+
+Within a snapshot, each content file must be referenced by at most one manifest entry across all manifests; otherwise, the snapshot has undefined behavior. Writers are not required to validate uniqueness at commit time.
Review Comment:
At most one **live** entry?
--
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: issues-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org