This is an automated email from the ASF dual-hosted git repository.
huaxingao pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg.git
The following commit(s) were added to refs/heads/main by this push:
new 9f266917b6 Spec: clarify the partition-spec metadata for Avro manifest
file (#13895)
9f266917b6 is described below
commit 9f266917b658931f3b704cd9c50b3f5d0da90cb7
Author: Steven Zhen Wu <stevenz...@gmail.com>
AuthorDate: Tue Aug 26 07:19:13 2025 -0700
Spec: clarify the partition-spec metadata for Avro manifest file (#13895)
* Spec: clarify the partition-spec metadata for Avro manifest file
* add link to the partition spec json parser in appendix c
* Update format/spec.md
Co-authored-by: Fokko Driesprong <fo...@apache.org>
---------
Co-authored-by: Fokko Driesprong <fo...@apache.org>
---
format/spec.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/format/spec.md b/format/spec.md
index 7def6e70ef..029b4f3821 100644
--- a/format/spec.md
+++ b/format/spec.md
@@ -609,14 +609,14 @@ A manifest stores files for a single partition spec. When
a table’s partition
A manifest file must store the partition spec and other metadata as properties
in the Avro file's key-value metadata:
-| v1 | v2 | Key | Value
|
-|------------|------------|---------------------|------------------------------------------------------------------------------|
-| _required_ | _required_ | `schema` | JSON representation of the
table schema at the time the manifest was written |
-| _optional_ | _required_ | `schema-id` | ID of the schema used to
write the manifest as a string |
-| _required_ | _required_ | `partition-spec` | JSON fields representation
of the partition spec used to write the manifest |
-| _optional_ | _required_ | `partition-spec-id` | ID of the partition spec
used to write the manifest as a string |
-| _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" |
+| v1 | v2 | Key | Value
|
+|------------|------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
+| _required_ | _required_ | `schema` | JSON representation of the
table schema at the time the manifest was written
|
+| _optional_ | _required_ | `schema-id` | ID of the schema used to
write the manifest as a string
|
+| _required_ | _required_ | `partition-spec` | JSON representation of only
the partition fields array of the partition spec used to write the manifest.
See [Appendix C](#partition-specs) |
+| _optional_ | _required_ | `partition-spec-id` | ID of the partition spec
used to write the manifest as a string
|
+| _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.
