Spec: V4 Adaptive Metadata Tree Spec Changes for Entry Structures#16025
Open
amogh-jahagirdar wants to merge 5 commits intoapache:mainfrom
Open
Spec: V4 Adaptive Metadata Tree Spec Changes for Entry Structures#16025amogh-jahagirdar wants to merge 5 commits intoapache:mainfrom
amogh-jahagirdar wants to merge 5 commits intoapache:mainfrom
Conversation
github-actions
Bot
added
the
Specification
- Collapse v1/v2/v3 separate tabs into single v1-v3 tab across all manifest sections - Add v4 tab to Data File Fields with content_entry, tracking, and deletion_vector structs using Write/Read columns - Reconcile v4 architecture prose from v4-amt-changes: root manifest concept, Parquet format, partition spec binding, updated terms/glossary Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
amogh-jahagirdar
force-pushed
the
v4-amt-changes
branch
from
544e59e to
f3d76cd
Compare
amogh-jahagirdar
changed the title
Contributor
Author
|
Two general working principals:
|
| | _optional_ | _optional_ | **`min-snapshots-to-keep`** | `int` | For `branch` type only, a positive number for the minimum number of snapshots to keep in a branch while expiring snapshots. Defaults to table property `history.expire.min-snapshots-to-keep`. | | ||
| | _optional_ | _optional_ | **`max-snapshot-age-ms`** | `long` | For `branch` type only, a positive number for the max age of snapshots to keep when expiring, including the latest snapshot. Defaults to table property `history.expire.max-snapshot-age-ms`. | | ||
| | _optional_ | _optional_ | **`max-ref-age-ms`** | `long` | For snapshot references except the `main` branch, a positive number for the max age of the snapshot reference to keep while expiring snapshots. Defaults to table property `history.expire.max-ref-age-ms`. The `main` branch never expires. | | ||
| === "v1 - v3" |
Contributor
Author
There was a problem hiding this comment.
If people like the two tabbed approach then we should get #14656 in first, that'll make this diff easier to review
amogh-jahagirdar
requested review from
RussellSpitzer,
danielcweeks,
nastra,
rdblue and
stevenzwu
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is one PR for V4 Adaptive Metadata Tree spec changes. The focus of this PR is to update the proposed entry structure in https://docs.google.com/document/d/1k4x8utgh41Sn1tr98eynDKCWq035SV_f75rtNHcerVw/edit?tab=t.wd1z5eeup025#heading=h.80fbnuij9rhg
There will be other PRs for updating the scan planning section, adding implementation notes for CDC etc.