Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Spec: Update v3 summary, add row lineage #12982

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.

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

Merged
merged 4 commits into from
May 7, 2025

Conversation

rdblue
Copy link
Contributor

@rdblue rdblue commented May 6, 2025

This adds a summary of row lineage changes to the section on v3 changes.

@github-actions github-actions bot added the Specification Issues that may introduce spec changes. label May 6, 2025
format/spec.md Outdated
@@ -1680,6 +1680,23 @@ Row-level delete changes:
* These position delete files must be merged into the DV for a data file when one is created
* Position delete files that contain deletes for more than one data file need to be kept in table metadata until all deletes are replaced by DVs

Row lineage changes:

* Writers must set the table's `next-row-id` and use the existing `next-row-id` as the `first-row-id` to create a new snapshot
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Writers must set the table's `next-row-id` and use the existing `next-row-id` as the `first-row-id` to create a new snapshot
* Writers must set the table's `next-row-id` and use the existing `next-row-id` as the `first-row-id` when creating new snapshots

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I considered this language, but I think it's more clear to use a singular snapshot. I don't want to imply that you would use next-row-id for multiple snapshots.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm 60:40 on my version versus yours so not a huge deal if you don't want to change it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. I committed this change. I think I'm just being pedantic.

@RussellSpitzer RussellSpitzer merged commit 3bb6a25 into apache:main May 7, 2025
2 checks passed
@RussellSpitzer
Copy link
Member

Thanks @rdblue for the important info, merged since this is just a restatement of information elsewhere in the spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Specification Issues that may introduce spec changes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants