iceberg v3 has to set first-row-id

[dentiny]

Is your feature request related to a problem or challenge?

Reading from the iceberg spec, it mentions

• 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 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

If I don't read it wrong, we should have next_row_id field in table metadata But I don't see it in TableMetadata, I'm wondering if we should add this field and set it on write?

Describe the solution you'd like

No response

Willingness to contribute

I can contribute to this feature independently

[c-thiel]

I started implementing V3 support today, first PR will be available tomorrow.

[hzxa21]

@c-thiel Do we have a tracking issue for the v3 support roadmap? We are also interested in the timeline and the TODO items. We can also help contribute to the v3 support.