danielcweeks commented on code in PR #15630: URL: https://github.com/apache/iceberg/pull/15630#discussion_r3120454497
########## format/spec.md: ########## @@ -123,9 +128,22 @@ Tables do not require random-access writes. Once written, data and metadata file Tables do not require rename, except for tables that use atomic rename to implement the commit operation for new metadata files. +### Relative Locations in Metadata + +Version 4 of the Iceberg spec adds support for relative locations in metadata, enabling tables to be relocated without rewriting metadata files. Key changes include: + +* Support for relative locations in all metadata tracked path fields, resolved against the table's base location +* The table `location` field becomes optional, allowing the table location to be: + * Provided by an owning catalog + * Inferred from the metadata file location or storage layout + * Supplied directly where necessary Review Comment: A better example might be for `register_table` where currently you must only provide the path to the `metadata.json` file. In v4, if the location field is omitted and you want to register a table, you'll need to supply both the `metadata.json` and independently the `table-location` to the register call. This is an example of something we'll have to update both in the REST spec and the register procedures. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
