JanKaul commented on issue #75: URL: https://github.com/apache/iceberg-rust/issues/75#issuecomment-1750077811
A typical usage would look something like the following: 1. Get `Table` with `load_table` operation. (This already fetches the `metadata_location` and `TableMetadata`) 2. Create transaction with the desired operations 3. Commit transaction with the `update_table` operation Generally you are right that the catalog could fetch the `metadata_location` and the `TableMetadata`. But in this case the data is already in memory through the `load_table` operation. It would therefore require 2 redundant network requests (one for `metadata_location` and one for `TableMetadata`) that could be avoided. Adding the `metadata_location` and `TableMetadata` references to the `TableCommit` struct just gives the `update_table` operation access to the information that is already there. Since `metadata_location` and `TableMetadata` are both present in the `Table` struct, it should simply be possible to pass their references to the `CommitTable` struct. -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
