You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iceberg.apache.org by ke...@apache.org on 2025/05/14 01:40:32 UTC
(iceberg) 01/01: typo: `next_row_id` -> `next-row-id`
This is an automated email from the ASF dual-hosted git repository.
kevinjqliu pushed a commit to branch kevinjqliu/typo
in repository https://gitbox.apache.org/repos/asf/iceberg.git
commit 6480c9bd42fa0d56c20c4c0f822221633e526977
Author: Kevin Liu <ke...@users.noreply.github.com>
AuthorDate: Tue May 13 21:40:22 2025 -0400
typo: `next_row_id` -> `next-row-id`
---
format/spec.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/format/spec.md b/format/spec.md
index c11dee43a5..a9ec8d127c 100644
--- a/format/spec.md
+++ b/format/spec.md
@@ -1685,7 +1685,7 @@ Row-level delete changes:
Row lineage changes:
* 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
- * When a table is upgraded to v3, `next_row_id` should be initialized to 0
+ * When a table is upgraded to v3, `next-row-id` should be initialized to 0
* When committing a new snapshot `next-row-id` must be incremented by at least the number of newly assigned row ids in the snapshot
* It is recommended to increment `next-row-id` by the total `added_rows_count` and `existing_rows_count` of all manifests assigned a `first_row_id`
* Writers must assign a `first_row_id` to new data manifests when writing a manifest list