Hi All, HiveTableOperations (BaseMetastoreTableOperations) does enforce Table UUID check when refreshing TableMetadata https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/BaseMetastoreTableOperations.java#L205
However, RESTTableOperations does not enforce Table UUID check when refreshing TableMetadata https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/rest/RESTTableOperations.java#L172 Is there any reason why they have different behaviors regarding Table UUID? Won’t that potentially cause issues when a table is dropped and recreated (but under a new UUID) on the server side, while the client is still holding the cached Table with old UUID? Thanks, Limin
