Re: [I] Concern about possible consistency issue in HiveCatalog's _commit_table [iceberg-python]

Fokko closed issue #588: Concern about possible consistency issue in HiveCatalog's _commit_table URL: https://github.com/apache/iceberg-python/issues/588 -- 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

Re: [I] Concern about possible consistency issue in HiveCatalog's _commit_table [iceberg-python]

Fokko commented on issue #588: URL: https://github.com/apache/iceberg-python/issues/588#issuecomment-2056289982 @HonahX Thanks for spotting this, and I agree that we should include the refreshing and updating of the metadata in the transaction. -- This is an automated message from the Ap

[I] Concern about possible consistency issue in HiveCatalog's _commit_table [iceberg-python]

HonahX opened a new issue, #588: URL: https://github.com/apache/iceberg-python/issues/588 ### Question Currently, the HiveCatalog's `_commit_table` workflow looks like: 1. load current table metadata via `load_table` 2. construct updated metadata 3. lock the hive table