Hi Team, I would like to bring up an issue I've identified regarding exception handling in the Iceberg REST Catalog.
Currently, if a table exists but its metadata file is missing, the *Iceberg REST Catalog* returns a *NoSuchTableException*. I believe this behavior is inconsistent with other catalogs, such as Glue and JDBC, which correctly return a *NotFoundException* in this scenario. This inconsistency can lead to confusion and make client-side error handling more complex. To address this, I've created a pull request that changes the REST Catalog's behavior to align with the other catalogs, ensuring a consistent *NotFoundException* is thrown when a table's metadata file is missing. You can find the proposed change here: https://github.com/apache/iceberg/pull/13143 Could you review and let me know if there are any questions/concerns? Thanks, Ashok
