feat: per-DataFile.first_row_id for v3 row lineage#2579
Open
Shekharrajak wants to merge 4 commits into
Open
Conversation
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
1 participant
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.
Which issue does this PR close?
What changes are included in this PR?
Closes the writer + reader gap for v3 row lineage: every ADDED DataFile in a v3 data manifest now gets a first_row_id stamped on write, and foreign-written manifests get one inherited on read. Combined with the existing TableMetadata.next_row_id / ManifestFile.first_row_id plumbing, this makes iceberg-rust spec-compliant for v3 row-id assignment end-to-end.
Java reference: ManifestReader.idAssigner (per-file inheritance) + SnapshotProducer row-id seeding.
Are these changes tested?
Unit tests