Repository navigation
Fixture: Add reference table for V3 row lineage - #26
Open
slachiewicz wants to merge 1 commit into
Open
slachiewicz wants to merge 1 commit into
slachiewicz wants to merge 1 commit into
Conversation
slachiewicz
force-pushed
the
v3-row-lineage-table
branch
from
November 19, 2026 17:37
1cafbd7 to
8e0a88c
Compare
slachiewicz
marked this pull request as ready for review
November 19, 2026 20:43
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
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.
Closes #13. Builds on #24, whose commit this branch carries until it merges; only the second commit is this change.
v3/row-lineage-parquet-datahas three snapshots. The first appendsa(row IDs 0 to 2). The second appendsbandcin one manifest (3 to 4, then 5), so a reader has to add the preceding file'srecord_count. The third is an overwrite that replacesawitha2, which stores row IDs 0 to 2 and sequence number 1 for the copied rows, a null sequence number for the updated row, and nulls for an added row that inherits_row_id9 (a2'sfirst_row_id6 plus position 3). A reader that ignores stored values returns 6 to 8 for the copied rows.expected/scan.jsonadds_row_idand_last_updated_sequence_numberkeyed by their reserved field IDs, and the README asks consumers to project them whererowscarries those keys. The generator gains anoverwritecommit whose rows may carry the two columns; the existing tables generate unchanged.The table is 52 KB over three commits; the overwrite writes a second manifest for the deleted entry.
Checked at every snapshot: an Iceberg Java 1.11.0 generic scan projecting both columns returns
expected/scan.json, and so does a read with no Iceberg library (plain Avro for manifest lists and manifests, DuckDB for Parquet). iceberg-go (1827440) resolves the same per-filefirst_row_idand data sequence numbers but cannot project_row_idyet. PyIceberg was not run.