Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spec: Clarify missing fields when writing #8672

Merged
merged 6 commits into from
Apr 26, 2024
Merged

Spec: Clarify missing fields when writing #8672

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
e3bc87c
Spec: Carify missing fields when writing
Fokko Sep 28, 2023
33271e7
Add manifest-list explicitly
Fokko Sep 28, 2023
d13491b
Update wording
Fokko Sep 28, 2023
00d1f73
Comments
Fokko Oct 8, 2023
340447b
Retain formatting
Fokko Oct 27, 2023
373f8b3
Thanks Steven
Fokko Apr 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions format/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,12 +128,12 @@ Tables do not require rename, except for tables that use atomic rename to implem

#### Writer requirements

Some tables in this spec have columns that specify requirements for v1 and v2 tables. These requirements are intended for writers when adding metadata files to a table with the given version.
Some tables in this spec have columns that specify requirements for v1 and v2 tables. These requirements are intended for writers when adding metadata files (including manifests files and manifest lists) to a table with the given version.

| Requirement | Write behavior |
|-------------|----------------|
| (blank) | The field should be omitted |
| _optional_ | The field can be written |
| _optional_ | The field can be written or omitted |
| _required_ | The field must be written |

Readers should be more permissive because v1 metadata files are allowed in v2 tables so that tables can be upgraded to v2 without rewriting the metadata tree. For manifest list and manifest files, this table shows the expected v2 read behavior:
Fokko marked this conversation as resolved.
Show resolved Hide resolved
Expand Down